Jump to content
This topic contains 29 posts. A summary containing the most significant posts is available

Featured Replies

Posted

So. I figured I'd try to upgrade my website over to version 5 and sadly it failed. I'll go into the back and get my login details posted for you all.

Unknown column 'post_featured' in 'SET'
#0 /chroot/home/mopar1973man/mopar1973man.com/html/system/Db/Db.php(1232): IPS\Db->preparedQuery() #1 /chroot/home/mopar1973man/mopar1973man.com/html/applications/core/setup/upg_5000057/upgrade.php(60): IPS\Db->update() #2 /chroot/home/mopar1973man/mopar1973man.com/html/applications/core/sources/Setup/Upgrade.php(648): IPS\core\setup\upg_5000057\Upgrade->step1() #3 /chroot/home/mopar1973man/mopar1973man.com/html/applications/core/sources/Setup/Upgrade.php(369): IPS\core\Setup\Upgrade->step1() #4 /chroot/home/mopar1973man/mopar1973man.com/html/applications/core/modules/setup/upgrade/upgrade.php(60): IPS\core\Setup\Upgrade->process() #5 /chroot/home/mopar1973man/mopar1973man.com/html/system/Helpers/MultipleRedirect/MultipleRedirect.php(104): IPS\core\modules\setup\upgrade\upgrade->IPS\core\modules\setup\upgrade\{closure}() #6 /chroot/home/mopar1973man/mopar1973man.com/html/applications/core/modules/setup/upgrade/upgrade.php(90): IPS\Helpers\MultipleRedirect->__construct() #7 /chroot/home/mopar1973man/mopar1973man.com/html/system/Dispatcher/Controller.php(139): IPS\core\modules\setup\upgrade\upgrade->manage() #8 /chroot/home/mopar1973man/mopar1973man.com/html/system/Dispatcher/Setup.php(261): IPS\Dispatcher\Controller->execute() #9 /chroot/home/mopar1973man/mopar1973man.com/html/admin/upgrade/index.php(38): IPS\Dispatcher\Setup->run() #10 {main}
/chroot/home/mopar1973man/mopar1973man.com/html/applications/core/setup/upg_5000057/upgrade.php::60

Solved by Mopar1973Man

Go to solution

Did you upgrade from 4.7.20 ?

  • Author

Yes sir. This was all up to date from the version 4.7.20. Then copied the files over and then proceeded to the /admin/upgrade and let it roll.

This looks like what happened here:

  • Author

OHHHH! Thank you so much! I'm going to get some rest and first thing in the morning and fix the database.

  • Author

So... After inserting the code below.

ALTER TABLE forums_posts

ADD COLUMN post_featured INT UNSIGNED NOT NULL DEFAULT 0;

This now creates a 500 server error code.

Double-checked all server settings and PHP settings.

As for digging into the Apache Error logs...

[Sun Mar 16 13:49:22 2025] [core:notice] [pid 1675:tid 139814005709120] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'

[Sun Mar 16 13:49:22 2025] [mpm_event:warn] [pid 1675:tid 139814005709120] AH00488: long lost child came home! (pid 840414)

[Sun Mar 16 13:49:22 2025] [mpm_event:warn] [pid 1675:tid 139814005709120] AH00488: long lost child came home! (pid 840415)

[Sun Mar 16 13:49:22 2025] [-:notice] [pid 845928:tid 139814005709120] FastCGI: process manager initialized (pid 845928)

[Sun Mar 16 14:00:52 2025] [mpm_event:notice] [pid 1675:tid 139814005709120] AH00493: SIGUSR1 received. Doing graceful restart

[Sun Mar 16 14:00:52 2025] [lbmethod_heartbeat:notice] [pid 1675:tid 139814005709120] AH02282: No slotmem from mod_heartmonitor

[Sun Mar 16 14:00:52 2025] [mpm_event:notice] [pid 1675:tid 139814005709120] AH00489: Apache/2.4.62 (AlmaLinux) OpenSSL/1.1.1k mod_watch/4.3 mod_fastcgi/2.4.6 configured -- resuming normal operations

  • Community Expert

All those errors are related to the apache being shut down, but did not start up again.

For more check out the following link from the apache docs.

https://httpd.apache.org/docs/2.0/stopping.html

Edited by Miss_B

  • Author

Yes. The Apache server restarts. Then I can restart the /admin/upgrade again and hit a wall of the apache shutting down with the 500 error code and then restarts again.

  • Community Expert
 

Yes. The Apache server restarts. Then I can restart the /admin/upgrade again and hit a wall of the apache shutting down with the 500 error code and then restarts again.

Do you manage your own Vps/Dedicated Box or are you on a shared hosting?

  • Author

Virtual Private Server (VPS) - 8 GB Ram, 160 GB Hard drive, 8 core.

  • Community Expert

I would very much advise on this point, reverting back to your backup. While I understand the other user managed to get past the issue by adding a column, thats not what we would usually advise. We would usually escalate so it can be looked at properly, and fixed going forward. I see in your case it didnt work, and you have the added issue that you also seem to have issues with your hosting crashing when an error is being recorded. So its compounding the issue

  • Author

Returned back to the original issue. DROPped the added column and back to the original error code.

Screenshot from 2025-03-17 09-50-52.png

Edited by Mopar1973Man

  • Community Expert
 

Returned back to the original issue. DROPped the added table and back to the original error code.

There is no point in doing this imo, because the upgrader doesn't add the aforementioned field itself. This is a bug. Meaning it doesn't matter how many times one restarts the upgrade process, one will always run into this issue, unless the bug is fixed.

That said, the best way imo to go about this in your case is to see if you can fix the apache issue.

Edited by Miss_B

  • Author
 

That said, the best way imo to go about this in your case is to see if you can fix the apache issue.

That's a tough one being the Apache is not providing much. I've copied the error.log and then cleared it so I can see real time errors. Error.log still blank. Still have the same error screen with the photo above. Nothing has changed per se. Version 4 ran just fine previously for 2 years on this server.

Screenshot from 2025-03-17 09-50-52.png

I need help to figure this all out and where to find more information to help you help me...

  • Community Expert
 

There is no point in doing this imo, because the upgrader doesn't add the aforementioned field itself. This is a bug. Meaning it doesn't matter how many times one restarts the upgrade process, one will always run into this issue, unless the bug is fixed.

That said, the best way imo to go about this in your case is to see if you can fix the apache issue.

The user OP was asked to do so, and then we can escalate as needed

 

That's a tough one being the Apache is not providing much. I've copied the error.log and then cleared it so I can see real time errors. Error.log still blank. Still have the same error screen with the photo above. Nothing has changed per se. Version 4 ran just fine previously for 2 years on this server.

Screenshot from 2025-03-17 09-50-52.png

I need help to figure this all out and where to find more information to help you help me...

Please leave it as it is now and ensure your access detail is up to date

  • Author

Should be up to date.... Let me know.

  • Management

This is fixed in 5.0.4 Beta 1, so if possible, use that version to upgrade to from v4.

  • Author

Ok... 5.0.4 Beta uploaded went farther into the install about the time it hit calendar for database it crashed again with 500 error code again. I'm stuck and don't know what it is now...

Screenshot from 2025-03-17 11-07-16.png

Edited by Mopar1973Man

  • Community Expert

You would want to get the error log entry from your server's error log.

  • Author
 

You would want to get the error log entry from your server's error log.

[Mon Mar 17 12:08:31 2025] [mpm_event:notice] [pid 1675:tid 139814005709120] AH00493: SIGUSR1 received. Doing graceful restart

[Mon Mar 17 12:08:32 2025] [lbmethod_heartbeat:notice] [pid 1675:tid 139814005709120] AH02282: No slotmem from mod_heartmonitor

[Mon Mar 17 12:08:32 2025] [mpm_event:notice] [pid 1675:tid 139814005709120] AH00489: Apache/2.4.62 (AlmaLinux) OpenSSL/1.1.1k mod_watch/4.3 mod_fastcgi/2.4.6 configured -- resuming normal operations

[Mon Mar 17 12:08:32 2025] [core:notice] [pid 1675:tid 139814005709120] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'

[Mon Mar 17 12:08:32 2025] [mpm_event:warn] [pid 1675:tid 139814005709120] AH00488: long lost child came home! (pid 854854)

[Mon Mar 17 12:08:32 2025] [mpm_event:warn] [pid 1675:tid 139814005709120] AH00488: long lost child came home! (pid 854855)

[Mon Mar 17 12:08:32 2025] [-:notice] [pid 1752197:tid 139814005709120] FastCGI: process manager initialized (pid 1752197)

[Mon Mar 17 12:08:52 2025] [mpm_event:notice] [pid 1675:tid 139814005709120] AH00493: SIGUSR1 received. Doing graceful restart

[Mon Mar 17 12:08:52 2025] [lbmethod_heartbeat:notice] [pid 1675:tid 139814005709120] AH02282: No slotmem from mod_heartmonitor

[Mon Mar 17 12:08:52 2025] [mpm_event:notice] [pid 1675:tid 139814005709120] AH00489: Apache/2.4.62 (AlmaLinux) OpenSSL/1.1.1k mod_watch/4.3 mod_fastcgi/2.4.6 configured -- resuming normal operations

[Mon Mar 17 12:08:52 2025] [core:notice] [pid 1675:tid 139814005709120] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'

[Mon Mar 17 12:08:52 2025] [mpm_event:warn] [pid 1675:tid 139814005709120] AH00488: long lost child came home! (pid 1752194)

[Mon Mar 17 12:08:52 2025] [mpm_event:warn] [pid 1675:tid 139814005709120] AH00488: long lost child came home! (pid 1752195)

[Mon Mar 17 12:08:52 2025] [-:notice] [pid 1753158:tid 139814005709120] FastCGI: process manager initialized (pid 1753158)

[Mon Mar 17 13:02:38 2025] [lbmethod_heartbeat:notice] [pid 1675:tid 139814005709120] AH02282: No slotmem from mod_heartmonitor

[Mon Mar 17 13:02:38 2025] [mpm_event:notice] [pid 1675:tid 139814005709120] AH00489: Apache/2.4.62 (AlmaLinux) OpenSSL/1.1.1k mod_watch/4.3 mod_fastcgi/2.4.6 configured -- resuming normal operations

[Mon Mar 17 13:02:38 2025] [core:notice] [pid 1675:tid 139814005709120] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'

[Mon Mar 17 13:02:38 2025] [mpm_event:warn] [pid 1675:tid 139814005709120] AH00488: long lost child came home! (pid 1753155)

[Mon Mar 17 13:02:38 2025] [mpm_event:warn] [pid 1675:tid 139814005709120] AH00488: long lost child came home! (pid 1753156)

[Mon Mar 17 13:02:38 2025] [-:notice] [pid 1791172:tid 139814005709120] FastCGI: process manager initialized (pid 1791172)

[Mon Mar 17 13:05:37 2025] [-:error] [pid 1791174:tid 139812493309696] (2)No such file or directory: [client 46.101.103.75:56742] FastCGI: stat() of "/chroot/home/mopar1973man/mopar1973man.com/html/php.fcgi" failed

  • Community Expert

You would need to provide the corresponding log entry, not the whole log. Note this may not be in the Apache log but the PHP log. Your hosting provider can assist you if you are unsure.

  • Author

This is from my /var/log/php-fpm Not much to even see there either.

[16-Mar-2025 03:36:03] NOTICE: error log file re-opened

[16-Mar-2025 12:40:16] NOTICE: Reloading in progress ...

[16-Mar-2025 12:40:16] NOTICE: reloading: execvp("/usr/sbin/php-fpm", {"/usr/sbin/php-fpm", "--nodaemonize"})

[16-Mar-2025 12:40:16] NOTICE: using inherited socket fd=8, "/run/php-fpm/www.sock"

[16-Mar-2025 12:40:16] NOTICE: fpm is running, pid 1626

[16-Mar-2025 12:40:16] NOTICE: ready to handle connections

[16-Mar-2025 12:40:16] NOTICE: systemd monitor interval set to 10000ms

[16-Mar-2025 12:48:57] NOTICE: Terminating ...

[16-Mar-2025 12:48:57] NOTICE: exiting, bye-bye!

[16-Mar-2025 12:48:57] NOTICE: fpm is running, pid 802846

[16-Mar-2025 12:48:57] NOTICE: ready to handle connections

[16-Mar-2025 12:48:57] NOTICE: systemd monitor interval set to 10000ms

[16-Mar-2025 13:42:05] NOTICE: Terminating ...

[16-Mar-2025 13:42:05] NOTICE: exiting, bye-bye!

[16-Mar-2025 13:42:05] NOTICE: fpm is running, pid 840869

[16-Mar-2025 13:42:05] NOTICE: ready to handle connections

[16-Mar-2025 13:42:05] NOTICE: systemd monitor interval set to 10000ms

[16-Mar-2025 14:00:59] NOTICE: Terminating ...

[16-Mar-2025 14:00:59] NOTICE: exiting, bye-bye!

[16-Mar-2025 14:00:59] NOTICE: fpm is running, pid 855074

[16-Mar-2025 14:00:59] NOTICE: ready to handle connections

[16-Mar-2025 14:00:59] NOTICE: systemd monitor interval set to 10000ms

[17-Mar-2025 13:02:42] NOTICE: Terminating ...

[17-Mar-2025 13:02:42] NOTICE: exiting, bye-bye!

[17-Mar-2025 13:02:42] NOTICE: fpm is running, pid 1791672

[17-Mar-2025 13:02:42] NOTICE: ready to handle connections

[17-Mar-2025 13:02:42] NOTICE: systemd monitor interval set to 10000ms

  • Community Expert

That would not be related to the error. Please contact your hosting provider if you need assistance in finding it.

  • Community Expert
 

NOTICE: error log file re-opened

This looks like it could be permission related. The log file seems to be non-writable.

  • Author

Here is what we found with my hosting company too.

[Mon Mar 17 13:01:21 2025] [proxy_fcgi:error] [pid 1753159:tid 139813281732352] [client 129.222.131.174:13077] AH01071: Got error 'PHP message: PHP Fatal error: Type of IPS\\collections\\_Item::$commentClass must be ?string (as in class IPS\\Content\\Item) in /chroot/home/mopar1973man/mopar1973man.com/html/applications/collections/sources/Item/Item.php on line 20', referer https://mopar1973man.com/admin/upgrade/index.php?controller=upgrade&key=052f9eb08ff0adced1a9d18848cc4aa0

[Mon Mar 17 13:03:04 2025] [proxy_fcgi:error] [pid 1791174:tid 139813463488256] [client 129.222.131.174:60722] AH01071: Got error 'PHP message: PHP Fatal error: Type of IPS\\collections\\_Item::$commentClass must be ?string (as in class IPS\\Content\\Item) in /chroot/home/mopar1973man/mopar1973man.com/html/applications/collections/sources/Item/Item.php on line 20', referer https://mopar1973man.com/admin/upgrade/index.php?controller=upgrade&key=dde9755821f6b880ee1f9321b0381bc0

[Mon Mar 17 13:03:06 2025] [proxy_fcgi:error] [pid 1791174:tid 139813463488256] [client 129.222.131.174:60722] AH01071: Got error 'PHP message: PHP Fatal error: Type of IPS\\collections\\_Item::$commentClass must be ?string (as in class IPS\\Content\\Item) in /chroot/home/mopar1973man/mopar1973man.com/html/applications/collections/sources/Item/Item.php on line 20', referer https://mopar1973man.com/admin/upgrade/index.php?controller=upgrade&key=dde9755821f6b880ee1f9321b0381bc0

[Mon Mar 17 13:07:01 2025] [proxy_fcgi:error] [pid 1791790:tid 139813463488256] [client 129.222.131.174:56582] AH01071: Got error 'PHP message: PHP Fatal error: Type of IPS\\collections\\_Item::$commentClass must be ?string (as in class IPS\\Content\\Item) in /chroot/home/mopar1973man/mopar1973man.com/html/applications/collections/sources/Item/Item.php on line 20', referer https://mopar1973man.com/admin/upgrade/index.php?controller=upgrade&key=cfd7b04049e534dfdb6294c8a90f099f

[Mon Mar 17 13:07:02 2025] [proxy_fcgi:error] [pid 1791790:tid 139813463488256] [client 129.222.131.174:56582] AH01071: Got error 'PHP message: PHP Fatal error: Type of IPS\\collections\\_Item::$commentClass must be ?string (as in class IPS\\Content\\Item) in /chroot/home/mopar1973man/mopar1973man.com/html/applications/collections/sources/Item/Item.php on line 20', referer https://mopar1973man.com/admin/upgrade/index.php?controller=upgrade&key=cfd7b04049e534dfdb6294c8a90f099f

Edited by Mopar1973Man

Recently Browsing 0

  • No registered users viewing this page.