Any idea what is causing this? /user/signup_save
--
Ken Rich
indiegospel.net
updated by @ken-rich: 11/05/23 02:51:27PM
JAMROOM
solved Signup Error
That means a fatal PHP error was encountered - look in the data/logs/error_log file - the most recent errors will be at the bottom.
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
Ken Rich:
I am not seeing anything in the error log,
It just says "No PHP Errors at this time"
I am not seeing anything in the error log,
It just says "No PHP Errors at this time"
Hmm - that doesn't make sense. That screen is from JR's custom PHP error handler it should also write a log entry. Make sure the data/logs directory is writable by the web user - could be the file can't be written do. See if you can temp set the directory permissions to 777, then try signing in again and see if the error_log file appears.
Also - if you are already logged in look for any CRI errors in your activity log.
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
The screenshot shows my error log in the admin panel is empty.
On the server, I have a data/logs/debug_log but no data/logs/error_log
The data/logs/debug_log has entries but the latest is last month and unrelated. The permissions are rw-r-r
On the server I also see an access log and an error log (under logs - not data/logs). The error log has something signup related at the end
I thought the issue might be related to the new CORE because I can't install 3 of my updates (users, profiles, search). However, I rolled back the core update and the signup issue persisted so I updated the core again.
--
Ken Rich
indiegospel.net
updated by @ken-rich: 08/06/23 03:34:19PM
On the server, I have a data/logs/debug_log but no data/logs/error_log
The data/logs/debug_log has entries but the latest is last month and unrelated. The permissions are rw-r-r
On the server I also see an access log and an error log (under logs - not data/logs). The error log has something signup related at the end
module.php(314): view_jrUser_signup_save()
#3 /usr/share/nginx/pinkbunnies.club/public_html/modules/jrCore-release-7.0.0/router.php(119): jrCore_run_module_view_function()
#4 {main}
thrown in /usr/share/nginx/pinkbunnies.club/public_html/modules/jrGeo-release-2.3.0/include.php on line 392" while reading response header from upstream, client: 174.113.80.37, server: pinkbunnies.club, request: "POST /user/signup_save HTTP/2.0", upstream: "fastcgi://unix:/run/php-fpm/jamroom.sock:", host: "pinkbunnies.club", referrer
--
Ken Rich
indiegospel.net
updated by @ken-rich: 08/06/23 03:34:19PM
Looks like it may be related to the Geo module - disable that one if you can and then make sure and do all the updates - you don't want to be partially updated. Let me know if that helps.
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
Scratch that - I just tried another integrity test and after that, my updates finally went in. So this network is good now with no Geo.
However, on my main network, the integrity check fails if I check "Repair Modules".
I used the new functionality to check individual modules and I can get them to pass if I don't try too many at once. All but the "Subscriptions" module - that one won't pass even if tried by itself.
The Reset Caches function also fails if "All template files" is checked.
Any ideas on those issues?
--
Ken Rich
indiegospel.net
However, on my main network, the integrity check fails if I check "Repair Modules".
I used the new functionality to check individual modules and I can get them to pass if I don't try too many at once. All but the "Subscriptions" module - that one won't pass even if tried by itself.
The Reset Caches function also fails if "All template files" is checked.
Any ideas on those issues?
--
Ken Rich
indiegospel.net
Yeah something is being flaky - I'm not sure but it sounds like you could be hitting a resource limit on the server? Are there any limits on your server put in place by your hosting provider? The fact that it originally stuck at:
"validating filesystem is prepared for updates"
Is the step where the marketplace module checks the modules/skins directory and ensures it has write permission before starting. It sounds like it could be bombing there.
I see you're running PHP via PHP-FPM - make sure you have enough worker processes so it doesn't hang.
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
"validating filesystem is prepared for updates"
Is the step where the marketplace module checks the modules/skins directory and ensures it has write permission before starting. It sounds like it could be bombing there.
I see you're running PHP via PHP-FPM - make sure you have enough worker processes so it doesn't hang.
--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
