badco's picture
badco - Sun, 2021/06/06 - 03:34

Hi, I have been struggling over this for a while now.

https://www.redmine.org/boards/2/topics/65335

As it says in the redmine topic, I am unfamiliar with all the tools that redmine uses so I amstruggling to diagnose what is going on here.

Any help would be appreciated :)

Forum: 
Support
badco's picture

badco - Sun, 2021/06/06 - 03:59

Error ID: 53fb8474

 

Following this reference to here:

[ E 2021-06-06 00:17:51.7784 23267/Tk age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /var/www/redmine: The application encountered the following error: Bundler::$
  Error ID: 53fb8474
  Error details saved to: /tmp/passenger-error-qz5xoX.html

Which leads me to the error file /tmp/passenger-error-qz5xoX.html

 

badco's picture

badco - Sun, 2021/06/06 - 04:03

https://paste.hardnet.nz/?52b09c6464c367ce#3bBTR6mY93zRLhwSge6Ga35SN7k7Y...

 

Jeremy Davis's picture

Jeremy Davis - Mon, 2021/06/07 - 06:56

It sounds like it's a bit late now, but ALWAYS take a backup before doing anything involving the inner workings of a server. That way, worst case scenario you can simply roll back to the previous working state.

Beyond that, from the "redmine error" file you posted on the Remine forums, it appears to be a permissions issue. Right near the end:

[ E 2021-05-02 10:55:32.7745 341/Tf age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /var/www/redmine: The application encountered the following error: Bundler::PermissionError (Bundler::
>PermissionError)
  Error ID: a52dfc12
  Error details saved to: /tmp/passenger-error-GqAAVs.html

THe file mentioned likely no longer exists, but it probably contains more details (maybe the specific file that it choked on?)

So perhaps just force all the files to be owned by the webserver? That should fix it:

chown -R www-data:www-data /var/www/redmine

Then restart Apache:

systemctl restart apache2
badco's picture

badco - Mon, 2021/06/07 - 08:35

It sounds like it's a bit late now, but ALWAYS take a backup before doing anything involving the inner workings of a server. That way, worst case scenario you can simply roll back to the previous working state.

Haha, I know right. I am still gettting used to Proxmox and it's workflow, and I also still have a lot of work to do to setup the backups and Proxmox Backup Server.

THe file mentioned likely no longer exists, but it probably contains more details (maybe the specific file that it choked on?)

So perhaps just force all the files to be owned by the webserver? That should fix it:

Good god, it was that simple! Thank you Jeremy!

 

Add new comment