mihol
Posts: 39
Joined: Wed May 09, 2012 6:55 pm
Location: Germany

issue after upgrade to 20200205 release

Sun Feb 09, 2020 1:04 pm

I'm not a Linux expert but build a NAS using OMV by going thru a tutorial .
It worked but when I applied the latest update today, raspbian stopped to let me login user pi.
symptom is: after boot sequence, GUI login screen appears , I enter user 'pi' and my password, press 'login' then screen goes black and after a while GUI login screen reappears.

during upgrade of ssh I was asked to apply new configuration or keep current config. I had selected 'keep current', might that be related?
Any idea?
Last edited by mihol on Sun Feb 09, 2020 5:40 pm, edited 5 times in total.

mihol
Posts: 39
Joined: Wed May 09, 2012 6:55 pm
Location: Germany

Re: issue after upgrade to 20200205 release

Sun Feb 09, 2020 5:19 pm

in addition to GUI login issue, OMV web gui now reports below error when I try to login there

Error #0:
OMV\Rpc\Exception: Failed to connect to socket: No such file or directory in /usr/share/php/openmediavault/rpc/rpc.inc:141
Stack trace:
#0 /var/www/openmediavault/rpc/session.inc(56): OMV\Rpc\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true)
#1 [internal function]: OMVRpcServiceSession->login(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)
#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)
#5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#6 {main}

User avatar
jojopi
Posts: 3566
Joined: Tue Oct 11, 2011 8:38 pm

Re: issue after upgrade to 20200205 release

Sun Feb 09, 2020 8:46 pm

mihol wrote:
Sun Feb 09, 2020 1:04 pm
symptom is: after boot sequence, GUI login screen appears , I enter user 'pi' and my password, press 'login' then screen goes black and after a while GUI login screen reappears.
One possible cause of the GUI failing to launch is that the root filesystem is full. Another is bad ownership in /home/pi due to previous inadvisable use of "sudo".

You should be able to press Ctrl+Alt+F2 and then login using text mode for further diagnosis using "df" and "ls -al".

mihol
Posts: 39
Joined: Wed May 09, 2012 6:55 pm
Location: Germany

Re: issue after upgrade to 20200205 release

Mon Feb 10, 2020 2:47 pm

jojopi wrote:
Sun Feb 09, 2020 8:46 pm
One possible cause of the GUI failing to launch is that the root filesystem is full.
...
You should be able to press Ctrl+Alt+F2 and then login using text mode for further diagnosis using "df" and "ls -al".
Ctrl+Alt+F2 got me logged in

Code: Select all

df
showed 100% use, therefore "root filesystem full" seems the root cause.
Open question: How to recover free disc space ?
in https://www.raspberrypi.org/blog/a-new- ... nt-1521853 Simon Long suggested

Code: Select all

sudo apt –fix-broken install
but that command gives an error, likely due to some typo that i couldn't figure out from reading the man page. Any hint welcome.

mihol
Posts: 39
Joined: Wed May 09, 2012 6:55 pm
Location: Germany

Re: issue after upgrade to 20200205 release

Mon Feb 10, 2020 2:55 pm

found instructions on https://blog.sleeplessbeastie.eu/2017/1 ... apt-cache/
sudo apt-get clean
reduced to 82% use

mihol
Posts: 39
Joined: Wed May 09, 2012 6:55 pm
Location: Germany

Re: issue after upgrade to 20200205 release

Mon Feb 10, 2020 3:19 pm

back in business now :)

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 30171
Joined: Sat Jul 30, 2011 7:41 pm

Re: issue after upgrade to 20200205 release

Mon Feb 10, 2020 3:23 pm

Also check /var/log for any large log files you no longer need.
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Working in the Applications Team.

Return to “Raspberry Pi OS”