Image problems in topics

(Saschaarthur) #1


Im using this discourse docker container (GitHub - discourse/discourse_docker: A Docker image for Discourse) more or less with default settings.

We running into the trouble that our previews(attached images) in the topics are not working properly.

I investigates a bit deeper and it seems that the html generator is not detecting the size of the image correctly:

<img src="xxx/uploads/default/original/1X/e21fa533c8b576334ce47208b471eb0676be4420.png" width="0" height="0">

The webserver itself returns the image correctly and if i live resize the html tag (with debug console), the image shows up.

This issues seems also only to happen in google chrome (latest version) firefox is working fine. Any idears?

Also if we edit the topic, the preview sizes in the html tag are correct…

(Jay Pfaffman) #2

Did you install using the install-cloud instructions?

(Saschaarthur) #3

well yeah, anything else you could consider for issues like this?

is there any config i can double check?

(Jay Pfaffman) #4

That’s odd. Did you import your data?

I think that a

./launcher enter app
rake posts:rebake

will solve the problem (I’ll do the same thing as editing the posts), but it doesn’t answer why the problem happened in the first place.

(Saschaarthur) #5

worked out for a couple of minutes and is now broken again… any further idears?

(Jay Pfaffman) #6

Hey, @zogstrip. Could any of your recent image commits have anything to do with this?

@saschaarthur, can you share a link to a topic on your site that exhibits this behavior?

(RĂ©gis Hanol) #7

Which “recent image commits”?

(Jay Pfaffman) #8

Well, that sounds like a no. This guy says that images are fine after a rebake, but soon thereafter the size changes to zero. I glanced at commits and saw you’d done something involving images.

(Saschaarthur) #9

figured out that were running on an old version, ill upgrade first maybe its related to this…
if it still persists will repost the link

(Saschaarthur) #10

running now on: 88ee2e35b59b7e9c6f7390c138b0fc7526a823cb problem still persists.

heres an example topic: Keepa - Amazon Price Tracker

(Jeff Atwood) #11

This means your Sidekiq background scheduler is not working. You have a broken install.

(Jay Pfaffman) #12

Have you done a rebake since you did the upgrade?

Did the sizes change back to zero after the rebake?

(Saschaarthur) #13

Thanks a lot for investigating.
Well we were running all time the docker containers and just pulling the latest versions. Any idears how this could have happened?

Easierst would be to reinstalls discuss / import a backup? or how should we solve it?

(Saschaarthur) #14

rebaking again now. lets see if it helps, thanks a lot ~

(Saschaarthur) #15

rebaking didnt helped, (1 call worked, then it got broken again) so problem still persists.

(Saschaarthur) #16

just noticed sidekiq is running…

~/discourse/discourse_docker # ps aux | grep side
root 1737 0.0 0.0 12944 1028 pts/1 R+ 22:19 0:00 grep side
ubuntu 17028 25.1 9.9 1843664 393260 ? Sl 21:48 7:47 sidekiq 4.2.4 discourse [5 of 5 busy]

could it be that sidekiq just takes hell lot of time to run and during this time images are broken?

(Dean Taylor) #17

You can check the status of Sidekiq by visiting your /sidekiq/ page for your install.

Top of the page will look something like this:

(Saschaarthur) #18

cant find detailed infos about whats failed, all other tabs in sidekiq only shows “OK” and “success”…

(Felix Freiberger) #19

Try having a look at /logs – are there any recent entries?

(Saschaarthur) #20

only plenty of warnings…

nothing related to the image problem…

So sidekiq is running and theres no errors related to this as far is i figured out… Any other idears?