11 Replies Latest reply on Apr 26, 2019 5:58 PM by Jan Cumps

    Problems with blog post

    Dudley Nelson

      Hey balearicdynamics

       

      cstanton got in touch with me about issues that you'd had with images when posting this blog: Art-a-Tronic Episode 12 . I'm responding here because I didn't want to add a comment and derail the conversation of the awesome project you've got there!

       

      I've been looking into the issues with images. I wish I had better answers for you.

       

      I've had a good look over the logs for this and there are issues with some of the images. It's not related to the gallery object itself, although the gallery is the most obvious and evident images failing. It looks like a batch of 14 images that you've uploaded at one point have all gone... weird during the upload of the images. I can tell you exactly when this happened (23rd April at 19:51:25 UK time) but I can't tell you exactly what happened because it's not clear from the logs. I'm hoping you might remember something screwy happen and fill in a few blanks.

       

      Going through the logs, the first sign of trouble is images failing to load from the database and key constraint issues. This will have caused a (probably highly annoying) red banner to appear frequently at the bottom while you were writing your post. The times within these posts are all UK times. I don't know what timezone you are in, but based on data in your profile I would suspect you're an hour ahead of us in the same timezone as Brussels, Madrid, Paris etc. So this would have started at 20:50 your time on 23rd April.

       

      sbs.log.6.gz:2019-04-23 19:51:25,689 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,691 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701786 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,693 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701787 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,694 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701788 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,696 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701803 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,697 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701912 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,699 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701913 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,700 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701914 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,702 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701916 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,703 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701917 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,705 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701918 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,706 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701919 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,707 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701920 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,708 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701921 could not be loaded from the database.
      

       

      These errors repeat again and again through out the logs. Searching for just one of these errors reveals you had this batch of errors again and again.

       

      sbs.log:2019-04-25 11:01:30,881 [http-nio-127.0.0.1-9001-exec-5] [RXZeI7eqiox4wBZcWr0oXxj4x0SikN4g:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.2.gz:2019-04-24 21:01:07,597 [http-nio-127.0.0.1-9001-exec-40] [PSAHjHpdPB0vZqWYZb9e0kGaPkuuIwim:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.2.gz:2019-04-24 22:28:15,555 [http-nio-127.0.0.1-9001-exec-25] [kaw380F0rjFFwX8O7vQV1ZGQW07mL5b6:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.2.gz:2019-04-24 23:27:35,574 [http-nio-127.0.0.1-9001-exec-32] [3FRcdlRPPQ0rym00MQzZGi9hgckOkNwL:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.3.gz:2019-04-24 11:10:03,697 [http-nio-127.0.0.1-9001-exec-19] [433226:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.3.gz:2019-04-24 11:12:43,923 [http-nio-127.0.0.1-9001-exec-36] [-1:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.3.gz:2019-04-24 11:20:23,398 [http-nio-127.0.0.1-9001-exec-13] [rq1kzI7BpseYBE6KUeq6plbdaTxCfaHL:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.3.gz:2019-04-24 16:18:37,085 [http-nio-127.0.0.1-9001-exec-37] [-1:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.4.gz:2019-04-24 02:48:09,744 [http-nio-127.0.0.1-9001-exec-26] [yDiz9dBBZZS760lQq5YdaIkSXfRtAz3j:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.4.gz:2019-04-24 07:57:25,287 [http-nio-127.0.0.1-9001-exec-29] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.4.gz:2019-04-24 07:57:42,320 [http-nio-127.0.0.1-9001-exec-21] [302646:REGULAR] ERROR com.jivesoftware.community.util.XMLUtils - Image 701776 could not be loaded from the database.
      sbs.log.4.gz:2019-04-24 08:01:36,141 [http-nio-127.0.0.1-9001-exec-21] [ROwRMLvIIamXvW0ZKkD9FUN0QoyVm11J:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 20:15:03,453 [http-nio-127.0.0.1-9001-exec-3] [302646:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 20:18:52,719 [http-nio-127.0.0.1-9001-exec-7] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 20:21:00,004 [http-nio-127.0.0.1-9001-exec-28] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 20:25:09,544 [http-nio-127.0.0.1-9001-exec-36] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 20:31:37,760 [http-nio-127.0.0.1-9001-exec-40] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 20:42:43,693 [http-nio-127.0.0.1-9001-exec-34] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 20:58:15,587 [http-nio-127.0.0.1-9001-exec-6] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 22:27:20,555 [http-nio-127.0.0.1-9001-exec-19] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 22:28:28,600 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 23:23:11,467 [http-nio-127.0.0.1-9001-exec-33] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-23 23:52:20,281 [http-nio-127.0.0.1-9001-exec-35] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-24 00:01:27,684 [http-nio-127.0.0.1-9001-exec-9] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-24 00:03:51,541 [http-nio-127.0.0.1-9001-exec-17] [BzzGn8GjbISnevBH1gPk5y7KWGhHyKUh:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-24 00:06:37,450 [http-nio-127.0.0.1-9001-exec-17] [xOH4JNF4cmczS7pJRZTWCZbRXxdhkG5f:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-24 00:06:47,088 [http-nio-127.0.0.1-9001-exec-33] [O2GeWz0cwJXOMLDYj0iTva551eXO9DsC:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-24 00:13:16,461 [http-nio-127.0.0.1-9001-exec-29] [tERiOGwWYKAw41Okc1DawqPZKXtjU5ak:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-24 00:32:36,608 [http-nio-127.0.0.1-9001-exec-21] [WvXVFUUoU2E0hEEIGGcs4ufuZGjwlHa5:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-24 00:49:29,802 [http-nio-127.0.0.1-9001-exec-38] [-1:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.5.gz:2019-04-24 02:12:12,096 [http-nio-127.0.0.1-9001-exec-8] [-1:REGULAR] ERROR com.jivesoftware.community.util.JiveServlet - Image 701776 could not be loaded from the database.
      sbs.log.6.gz:2019-04-23 19:51:25,689 [http-nio-127.0.0.1-9001-exec-38] [302646:REGULAR] ERROR com.jivesoftware.community.content.draft.impl.DbDraft - Image 701776 could not be loaded from the database.
      

       

      You appear to have been the only one affected by this, and the only thing it has affected is this one post and those 14 images.

       

      I can tell you from going through your post exactly which images this is affecting, and one solution here would be for you to send us those images and we'll get this sorted out. But it might be easier to just reupload these particular images and reembed them.

       

      For clarity, the images that are missing from your post are:

       

      701776 Mirror9.JPG

      701786 Mirror10.JPG

      701787 Mirror11.JPG

      701788 Mirror12.JPG

      701803 MirrorSensor+Sketch.jpeg

      701912 MirrorSensor+Front.png

      701913 MirrorSensor+Back.png

      701914 IMG_20190419_085408.jpg

      701916 IMG_20190419_091923.jpg

      701917 IMG_20190419_091935.jpg

      701918 IMG_20190419_095306.jpg

      701919 IMG_20190419_095951.jpg

      701920 IMG_20190419_100004.jpg

      701921 IMG_20190419_102622.jpg

       

      Now, there is another piece of the puzzle that I have no doubt you are saying to yourself right now - "But I can see the images just fine in the blog post? They are there!" Your comment on your blog post says as much, and a picture says a thousand words.

       

       

      They are showing for you because they are cached for you (and only you) by either our Content delivery network, or more likely in your browser.

       

       

      It could well be that if you go to your blogpost and do a ctrl-F5 (Cmd-f5 on a mac) then the images will suddenly disappear. It could be they don't, but I am absolutely certain that the images are cached somewhere between our servers and your browser.

       

      The reason they would disappear is not because they delete at that point, they disappear because we don't have those images. I can guarantee that at some point in the future, when whatever is caching those images attempts to renew the cache, those images will disappear.

       

      It would be great if we can get this solved. Essentially all that needs doing is for the images I've listed above to be reinserted into the post and put back in the correct spots. I can do that for you, but you may well find it is easier to do it yourself than it is to email those images over to me.

       

      I don't know how you want to proceed here. I can only apologise for the hassle. I wish I had more answers, but without more details on what went wrong (which I don't think I am going to get unless we can find a way of reproducing the issue) I really can't guarantee anything.

       

      A thousand words

        • Re: Problems with blog post
          balearicdynamics

          Hello Dudley,

           

          thank you for the clear explanation. The only relatively strange thing I can remember is that after one of my "save draft" commands I saw a message on a landing page that the system was under maintenance. Then I just reloaded the page and completed the post.

           

          It is not a big problem to reload the images on the post, sure is faster and more efficient if I do it than sending the images and spending the same time in two. Just to be sure, as I will do it later, you mean that I can delete the image and reload it without any change? I hope I can do it one image at a time, as it is easier for me to find again the right ones.

           

          Thank you for your time. Enrico

          • Re: Problems with blog post
            balearicdynamics

            Hi, I have a short update.

             

            I tried to edit the post and started removing and uploading the images again and as already noticed, every few seconds I get the message bar as shown in the below image. At this point, to avoid making more damage I stopped the editing (but I have saved it, replacing the first two images shown after the video.

             

            Some idea? I the image replacing safe also with this annoying bar?

             

            Enrico

             

              • Re: Problems with blog post
                Jan Cumps

                I’m getting the red bar on and off today too. Refreshing does not help. I get it most when I check the inbox.

                2 of 2 people found this helpful
                  • Re: Problems with blog post
                    balearicdynamics

                    If I am not wrong, this issue has created several kinds of problems time ago (maybe 4 or 5 update steps ago), it was the period when the inbox was always showing 1 unread message while all was read; this last issue has not occurred to me now.

                     

                    Enrico

                    1 of 1 people found this helpful
                      • Re: Problems with blog post
                        Dudley Nelson

                        Not all red bars are the same. The one on the inbox will almost certainly be unrelated to these (although it might be the same). We've stopped using one of our analytics tools (pardot) and the code we have in place for that is now erroring and it's causing a lot of system wide errors at the moment. It might be that the errors you're getting in the inbox is related to that, but it could also be that you've got something else entirely.

                         

                        Also, my admin rights allow me to do a lot of things as a user, but one thing I cannot do is to look at your inbox.

                         

                        The inbox is prone to red bars because you can browse through a lot of content in a short amount of time. Was it a particular piece of content that errors, and is it reproducable? If you select that piece of content and get a red bar, then go to a different piece of content and then come back to it again, does it red bar a second time? If so, send me that bit of content over and I'll take a look

                         

                        Otherwise, if you're getting red bars, especially if they are reproducable, I'd welcome you posting it here in F&S

                        2 of 2 people found this helpful
                          • Re: Problems with blog post
                            balearicdynamics

                            Hello Dudley,

                             

                            I have removed and uploaded the images again, also making some changes to having the changes visible. I have done the job from my office Mac, different machine and different network. I never got the red bar making the changes. Consider that also from this site I was seeing correctly the post, that is what sounds really strange to me. Please, let me know if something now has changed.

                             

                            Thank you in advance.

                            Enrico

                              • Re: Problems with blog post
                                Dudley Nelson

                                First things first, I've checked and we're all good now Everything is working fine and all is good

                                 

                                That it works on a different machine / different network tells me it must have been cached at the Akamai level. Akamai maintain caches in most major ISPs and it's feasible that your office ISP and your home ISP are the same, or are served by the same cache. Caching is a wonderful invention and the internet couldn't exist without it, but it can really hinder trying to work out what is going wrong or what is erroring.

                                 

                                But for akamai to have cached it, it means at some point you've uploaded it to our servers and we've passed the image back to you.

                                 

                                I'm into the realm of guessing now, but I would guess that what happened here is that you uploaded your images and these were associated with a draft post. You then had the site unavailable message and reloaded from a draft, but for some reason when the system discarded that draft, it also discarded the images associated with the draft. But because you'd been served those images previously by us, Akamai cached those images and made it appear like it was working even though they were now in error.

                                 

                                We're right on an edge case here. I don't think this is something happens often - you post a lot of blogs and I believe this is the first time you've had image issues. And I certainly don't think I'm going to be able to get this reproducable any time soon. I can have a look over the draft code, it's feasible we've got a bug in drafts code - we delete the images associated with a draft when the draft is deleted, and while in most operations this is working fine, I think you've found an edge case in which the draft or the images are being erroneously deleted when they should be kept.

                                 

                                And I really cannot help feel that I'm missing something really obvious that went wrong here. I get the feeling that at some point down the road I'm going to discover some fact or realise that some component isn't working quite right and all the confusion on this particular problem will suddenly all make sense.

                                 

                                However, everything is good now and I'm glad we've got this sorted in the short term, even if I'm still not much closer to working out how this all happened in the first place.

                                2 of 2 people found this helpful
                              • Re: Problems with blog post
                                Jan Cumps

                                I had the exact same red bar that balearicdynamics shows above continuously today when creating this blog post, dudley.nelson: HARTING MICA: Develop and Debug a C GPIO Example in Eclipse - Part 3: Eclipse Configuration on Windows.

                                It didn't block me from saving the post as draft each time, and now that I published it, it seems to be ok - including images.

                                The red bar must have appeared at least 10 times while editing the article. It is uncommon - I didn't experience this lately.

                          • Re: Problems with blog post
                            Dudley Nelson

                            Yeah, editing the post will cause lots of red error bars to appear. It does this because you're getting the error I listed above appear. It's trying to load in those fourteen images and failing, and when it fails it pops up the red error. You'll get them as long as the html pointing at the erroring images remains.

                             

                            Do you want me to go through it and replace them out with a placeholder that you can easily find? That would take me no time to do and would solve the annoying red bar

                            1 of 1 people found this helpful