Man in a van wrote:
> Well,
>
> I have tried another install and SSH'd into the cubietruck, but then
> realised I did not knowthe command line instruction to see what was
> happening.:mad:
>
> I have attached a copy of the text displayed during the install (must be
> similar, I would think) and the "_*-failure-*_" word can be seen towards
> the end.
>
> atb
>
> Ronnie
I assume you mean these last lines:
Code:
--------------------
Apr 05 13:20:02 soa-cubietruck soa-firstboot.sh[885]: Created symlink from
/etc/systemd/system/multi-user.target.wants/soa-web.service to
/usr/lib/systemd/system/soa-web.service.
Apr 05 13:20:02 soa-cubietruck systemd[1]: Reloading.
Apr 05 13:20:03 soa-cubietruck systemd[1]: Starting Squeeze on Arch Web
Interface...
Apr 05 13:20:03 soa-cubietruck systemd[1]: Failed to set
memory.limit_in_bytes on : Invalid argument
Apr 05 13:20:03 soa-cubietruck systemd[1]: Started Squeeze on Arch Web
Interface.
Apr 05 13:20:14 soa-cubietruck soa-web.lua[1999]: luajit:
/usr/share/lua/5.1/turbo/sockutil.lua:179: [tcpserver.lua Errno 98] Could not
bind to address. Address already in use
Apr 05 13:20:14 soa-cubietruck soa-web.lua[1999]: stack traceback:
Apr 05 13:20:14 soa-cubietruck soa-web.lua[1999]: [C]: in function 'error'
Apr 05 13:20:14 soa-cubietruck soa-web.lua[1999]:
/usr/share/lua/5.1/turbo/sockutil.lua:179: in function 'bind_sockets'
Apr 05 13:20:14 soa-cubietruck soa-web.lua[1999]:
/usr/share/lua/5.1/turbo/tcpserver.lua:118: in function 'listen'
Apr 05 13:20:14 soa-cubietruck soa-web.lua[1999]:
/usr/share/lua/5.1/turbo/web.lua:916: in function 'listen'
Apr 05 13:20:14 soa-cubietruck soa-web.lua[1999]: /usr/bin/soa-web.lua:1155:
in main chunk
Apr 05 13:20:14 soa-cubietruck soa-web.lua[1999]: [C]: at 0x0000cb6c
Apr 05 13:20:14 soa-cubietruck systemd[1]: soa-web.service: main process
exited, code=exited, status=1/FAILURE
Apr 05 13:20:14 soa-cubietruck systemd[1]: Unit soa-web.service entered
failed state.
Apr 05 13:20:14 soa-cubietruck systemd[1]: soa-web.service failed.
Apr 05 13:20:14 soa-cubietruck sudo[1888]: pam_unix(sudo:session): session
closed for user root
Apr 05 13:20:14 soa-cubietruck sudo[1885]: pam_unix(sudo:session): session
closed for user aur
Apr 05 13:20:14 soa-cubietruck soa-firstboot.sh[885]: ~
Apr 05 13:20:16 soa-cubietruck soa-firstboot.sh[885]: soa-web
Apr 05 13:20:16 soa-cubietruck soa-firstboot.sh[885]: squeezelite
Apr 05 13:20:16 soa-cubietruck soa-firstboot.sh[885]: Created symlink from
/etc/systemd/system/dbus-org.freedesktop.Avahi.service to
/usr/lib/systemd/system/avahi-daemon.service.
Apr 05 13:20:16 soa-cubietruck soa-firstboot.sh[885]: Created symlink from
/etc/systemd/system/multi-user.target.wants/avahi-daemon.service to
/usr/lib/systemd/system/avahi-daemon.service.
Apr 05 13:20:16 soa-cubietruck systemd[1]: Reloading.
Apr 05 13:20:16 soa-cubietruck soa-firstboot.sh[885]: Created symlink from
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket to
/usr/lib/systemd/system/avahi-daemon.socket.
Apr 05 13:20:17 soa-cubietruck soa-firstboot.sh[885]: /boot ~
Apr 05 13:20:17 soa-cubietruck soa-firstboot.sh[885]: cp: cannot stat
'script.bin': No such file or directory
Apr 05 13:20:17 soa-cubietruck soa-firstboot.sh[885]: E: fexc: script.bin: No
such file or directory
Apr 05 13:20:17 soa-cubietruck soa-firstboot.sh[885]: ~
Apr 05 13:20:17 soa-cubietruck soa-firstboot.sh[885]: soa-web
Apr 05 13:20:17 soa-cubietruck soa-firstboot.sh[885]: Removed symlink
/etc/systemd/system/multi-user.target.wants/soa-firstboot.service.
Apr 05 13:20:17 soa-cubietruck systemd[1]: Reloading.
Apr 05 13:20:18 soa-cubietruck soa-firstboot.sh[885]: SOA Install Complete
Apr 05 13:20:20 soa-cubietruck systemd[1]: Stopping Session c1 of user root.
Apr 05 13:20:20 soa-cubietruck sshd[15733]: Exiting on signal 15
Apr 05 13:20:20 soa-cubietruck sshd[15733]: pam_unix(sshd:session): session
closed for user root
Apr 05 13:20:21 soa-cubietruck systemd[1]: Stopped Session c1 of user root.
--------------------
The fact the soa-web service failed need not necessary mean a fatal bug,
there may still be a partially working system on your cubietruck. I take
it at this stage you've lost any network connection to your cubietruck.
That would suggest there is at least a network configuration problem in
the current install process. I'm not sure what the "-cp: cannot stat
'script.bin': No such file or directory-", message indicates. Without
attaching a monitor and keyboard to the Cubietruck during the install
and seeing what state the device is in when you get to the "SOA Install
Complete" message, I'd be guessing. I'll have a look at the install
script to see if I can make any sense of it.
------------------------------------------------------------------------
Krisbee's Profile: http://forums.slimdevices.com/member.php?userid=59080
View this thread: http://forums.slimdevices.com/showthread.php?t=101624
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix
