Concerto: Web application could not be started

[Scott Broussard]

Hi Vangelius,

My Concerto digital signage webserver was working fine and then suddenly today, I got this error msg on all my display medias:

Have you seen this msg before? Can you help?

Thanks,

--

Scott Broussard

IT Administrator 

Bern Dibner Library of NYU

5 Metrotech CTR. Floor 3, Room 317

Brooklyn, NY 11201

1-646-997-3578

[Marvin Frederickson]

That code is related to reading the config file from within the /usr/share/concerto/.bundle/ directory.  Does www-data have read access to that directory/file?

Is there anything in the

  tail -800 /usr/share/concerto/log/production.log

that might help us figure out what is going on?

Have you updated anything on that machine lately that might have impacted this?

--
You received this message because you are subscribed to the Google Groups "Concerto Digital Signage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concerto-digital-signage+unsub...@googlegroups.com.
To post to this group, send email to concerto-digital-signage@googlegroups.com.
Visit this group at https://groups.google.com/group/concerto-digital-signage.
For more options, visit https://groups.google.com/d/optout.

[rodrigo....@gmail.com]

Hi Scott, I am not really sure. if you are not using the latest version of Concerto server try upgrade it to the latest version of Concerto (april 2017: Concerto 2.3.4) use for this the terminal through SSH if you want. The backup of the signage adds should have been in place i hope you have the backup of the images intact. Okey, If still getting errors maybe reinstall the server but after that date do not upgrade the concerto production server without before trying doing as below system developing management tip. Talking about some different approach, another Approach to security, this tip is for Concerto Server using Unix/Linux systems: you can protect the server and clients using UFW and with that control the “What, Who and How" over all access in between "Concerto and their clients”. UFW helps decreasing the urgent security aspects and other needs that your systems and their dependencies OBEY to the need of UPDATE their systems continuously, BUT when you control the traffic IN and OUT in between Concerto and their clients and of course ALLOW Access to the concerto admins then you don’t have anymore the OBEY urging of install AT ONCE the needed systems updates, because you system is already well protected through UFW. Then, you can try the below test system implementation (of Concerto Server) in another computer and do all the test updates/upgrades there with the Concerto server/Linux/ connection with RPI, PCs and other clients, all this before doing it at the vital production Concerto server you are using in your signage system. 

Prevent the urges of the obeys of immediately-do-the-update-upgrade through tip here under:

System developing management tip: Create a Parallel Concerto production server and use it as a kind of Concerto server test lab and test there your upgrades BEFORE doing it with your original Concerto production server. Changing your Concerto production server version status is risky so with the test lab in place is a bit safer because you don’t want "fatality by deploying updates” syndrom that sometimes happens when changing your original production systems “on the fly”. But I don’t know if you did update the system before the crasch, so, it was very general speaking about it up here.

Good luck,

Greetings!

Vangelius

2017-04-07 18:53 GMT+02:00 Scott Broussard:

Hi Vangelius,

Have you seen this msg before? Can you help?

Thanks,

Den fredag 7 april 2017 kl. 18:53:58 UTC+2 skrev Scott Broussard:

Hi Vangelius,

My Concerto digital signage webserver was working fine and then suddenly today, I got this error msg on all my display medias:

[andrew...@gmail.com]

Hey Scott,

This is probably too late for you to care, but I've experienced that exact same error once or twice, most recently after expanding the disk size of my Concerto VM.  Here's the song and dance I usually have to go through to get it functional again:

sudo mv /usr/share/concerto/Gemfile.lock /usr/share/concerto/Gemfile.lock.bak
sudo RAILS_ENV=production /usr/share/concerto/bin/bundle install

The latter command usually tanks and I have resolve some Gem dependencies (despite making no other config changes to Concerto).  So I'll go into /usr/share/concerto/Gemfile-plugins and see if there's anything weird in there, which there sometimes is (stuff reverting to older versions, usually).  Then I repeat the lock file removal and bundle install.

It can take a bit of work, but it usually works eventually.

[Scott Broussard]

Thanks Andrew!