Hi at all!
Since yesterday night I can no longer sign in into OMV!
If use wrong credentials, it gave error. If I use the right one instead it simply releoad the login page asking me to insert them again!
How can I do to resolve?
I can login without problem with SSH, the only problem is the webinterface
Can't login with correct credentials on web interface
-
- gelöst
- OMV 2.x
- Blabla
-
-
The root drive might be full. What is the output of: df -h
-
-
I would delete the .1 files to start. Those are archives. I would also look in syslog to see what is logging so much. Maybe by posting tail -n 200 /var/log/syslog, I could tell.
-
I would delete the .1 files to start. Those are archives. I would also look in syslog to see what is logging so much. Maybe by posting tail -n 200 /var/log/syslog, I could tell.
I did a Tail on syslog.1 and kern.log.1,
this was the error that i found in both of them:CodeJul 16 11:09:07 NAS kernel: [ 320.973111] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160108/evgpe-592) Jul 16 11:09:07 NAS kernel: [ 320.974151] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
with your command this are the error that i had:
Code
Alles anzeigenJul 18 00:59:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 00:59:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:00:01 NAS /USR/SBIN/CRON[14207]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1) Jul 18 01:00:01 NAS rrdcached[2632]: Received FLUSHALL Jul 18 01:00:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:00:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:01:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:01:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:02:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:02:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:03:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:03:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:04:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:04:12 NAS rrdcached[2632]: flushing old values Jul 18 01:04:12 NAS rrdcached[2632]: rotating journals Jul 18 01:04:12 NAS rrdcached[2632]: started new journal /var/lib/rrdcached/journal/rrd.journal.1468796652.581411 Jul 18 01:04:12 NAS rrdcached[2632]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1468789452.581409 Jul 18 01:04:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:17:01 NAS /USR/SBIN/CRON[14562]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jul 18 01:17:01 NAS postfix/postsuper[14565]: fatal: scan_dir_push: open directory hold: No such file or directory Jul 18 02:09:01 NAS /USR/SBIN/CRON[15490]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)
-
What kernel are you using?
-
4.5.7, because I have the latest chipset, and the 3.16 is not compatible with them
-
Try the following command:
echo "disable" > /sys/firmware/acpi/interrupts/gpe6F
If that fixes the problem, then I would add that line /etc/rc.local
-
how can I know if the command is working? I deleted both .1 logs, but a sill have a 8,2GB syslog
-
The tail command shows the end of the log and the messages are timestamped. If the messages stop appearing, then it is fixed.
To make it simple:
echo "disable" > /sys/firmware/acpi/interrupts/gpe6F
echo "" > /var/log/syslog (this will wipe syslog but it is not really that important)
tail -f /var/log/syslog
The last command will allow you to watch all new syslog entries. If you don't see any of the error messages, add it to /etc/rc.local. ctrl-c exits out of tail. -
I have again the same problem
here's the log:
13G /var/log/syslog
5.5G /var/log/messages
5.5G /var/log/kern.log
505M /var/log/messages.1
505M /var/log/kern.log.1
235M /var/log/messages.2.gz
235M /var/log/kern.log.2.gz
123M /var/log/syslog.1this time I have endlessy this error into syslog:
Aug 1 07:10:39 NAS kernel: [ 7222.875427] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160108/evgpe-592)
Aug 1 07:10:39 NAS kernel: [ 7222.876384] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
Aug 1 07:10:39 NAS kernel: [ 7222.876385] ACPI Error: Method parse/execution failed [\_GPE._L6F] (Node ffff8802654e36f8), AE_NOT_FOUND (20160108/psparse-542) -
Did you add echo "disable" > /sys/firmware/acpi/interrupts/gpe6F to /etc/rc.local? Otherwise, it needs to be reset every time you reboot.
-
uops, totally forgot to add that like to the file! I did it now
-
Sorry to resume this thread again, but this time have a problemwith the "in" folder:
Code
Alles anzeigenroot@NAS:/var# du -sh /* | sort -hr [/tt] 349G /media [/tt] 26G /in [/tt] 1.7G /usr [/tt] 397M /lib[/tt] root@NAS:/var# du -sh /in/* | sort -hr [/tt] 23G /in/in [/tt] 1.7G /in/usr [/tt] 397M /in/lib[/tt] root@NAS:/var# du -sh /in/in/* | sort -hr [/tt] 23G /in/in/in [/tt] 64M /in/in/boot [/tt] 15M /in/in/bin[/tt]
If I try to add other /in in the command, it always give me the same error
-
What is the "in" folder? Never seen that before...
-
I think it was made by the backup plugin, i removed it and OMV still works
-
openmediavault-backup? It definitely does not make that folder.
-
You saw what weas there too. It was like and endlessy replication of the first folder probably a bug or me doing something wrong!
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!