I went to check for updates and cannot log in. i get this error
Error 500 failed to start session.
i can telnet into root, any ideas?
I went to check for updates and cannot log in. i get this error
Error 500 failed to start session.
i can telnet into root, any ideas?
Have you tried clearing your browser cache or logging in with a different browser?
yes, chrome, edge, different PC, same result
Are you simply getting a 500 error? Or are you getting a login loop? If it's the latter, your system disk might be full.
i get this error: Error 500 failed to start session.
then the error disappears and i am still at the login screen.. does not look like a loop to me and the /dev/sde1 folder is only at 4%.
tried clearing the cache for the browser, tried another browser, PC. still the same...
i get this error: Error 500 failed to start session.
then the error disappears and i am still at the login screen..
That's the loop.
the /dev/sde1 folder is only at 4%.
Is /dev/sde1 the system disk? I would check the instructions in the guide I linked.
i beleive it is and one are full, largest is /dev/md0 at 18%:
root@mediavault2:/# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 972904 0 972904 0% /dev
tmpfs 200308 13272 187036 7% /run
/dev/sde1 242970012 7062852 223492184 4% /
tmpfs 1001524 0 1001524 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 1001524 0 1001524 0% /tmp
/dev/md0 11627129648 1977797548 9649315716 18% /srv/dev-disk-by-uuid-853b5d8d-d16e-426d-9253-3248901613f2
It appears the system disk is not full. Try running omv-firstaid and resetting the failed login attempt counter.
done but no change unfortunately.
the weird thing is there is no real description of the fault, just this
500 - Internal Server Error Failed to start session.
i also used OMV-firstaid to check the configuration status file, checks OK but if i check the RRD database it says there are timestamps in the future. could this be the cause?
that last result prompted me to check something, i can write a file to the array but find that the time stamp is an hour back, before the daylight savings channge. so i try to set the timezone using omv-firstaid but get this error:
Updating time zone. Please wait ...
{'response': None, 'error': {'code': 0, 'message': 'Unknown error', 'trace': 'OM V\\Config\\DatabaseException: Unknown error in /usr/share/php/openmediavault/con fig/databasebackend.inc:461\nStack trace:\n#0 /usr/share/php/openmediavault/conf ig/databasebackend.inc(243): OMV\\Config\\DatabaseBackend->commit()\n#1 /usr/sha re/php/openmediavault/config/database.inc(269): OMV\\Config\\DatabaseBackend->re place()\n#2 /usr/share/openmediavault/engined/rpc/system.inc(367): OMV\\Config\\ Database->set()\n#3 [internal function]: Engined\\Rpc\\System->setTimeSettings() \n#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_ array()\n#5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\\Rpc\\ServiceAbst ract->callMethod()\n#6 /usr/sbin/omv-engined(546): OMV\\Rpc\\Rpc::call()\n#7 {ma in}', 'http_status_code': 500}}
ERROR: Unknown error
timestamps in the future
Perhaps you've found the cause of your problem. I've seen that error before on the forum. Do a search and you'll find some threads discussing it.
Here's one of those threads. Diagnostics -> Performance Statistics - All graphs are not showing any data after updating to OMV 6.4.7-1
this is all strange, using the omv-firstaid tool i try to set the time zone and get an error.
when i try to check the rrd database i get the message about timestamp in the future but when i try to delete it i get an error about read-only system file.
then i tried apt-get install rrdtool --reinstall as in the post you sent me and that also gives me a read-only error.
am i doing something wrong?
i also went to look at the hw clock and system clock. they seem set properly but the hardware clock is UTC. could that be an issue? if i try to change it i get the warning about system read only file.
in the end i used commands to set time and timezone and then rebooted. i then noticed it did not boot so i connected a monitor to see that it was stuck in a shell saying to run fsck manually. i did so and it is now running normally after repearing some system files. go figure.
That could explain everything that's happened to you. If your system disk isn't in good condition, I would replace it as soon as possible.
Don’t have an account yet? Register yourself now and be a part of our community!