[Gta04-owner] Debian Jessie on GTA04

[Dr. H. Nikolaus Schaller]

Hi,

Am 17.12.2014 um 20:08 schrieb Rico Rommel <rico at bierrommel.de>:

> Am Mittwoch, 17. Dezember 2014, 18:54:40 schrieb Dr. H. Nikolaus Schaller:
>> Hi,
>> I am trying to make Debian Jessie (because it is now "almost stable”) run on
>> the GTA04.
>> 
>> To get it I used the bootstrap tool [1] we have on our wheezy system to get
>> a fresh rootfs and merged our 3.18.0 kernel+modules.
>> 
>> The system boots to a console (without login!). And after apt-get
>> openssh-server I can even ssh into the GTA04.
>> 
>> But I have problems to get the systemd run properly.
>> 
>> The key symptom is
>> [   14.480712] systemd-update-utmp[1402]: Failed to get D-Bus connection: No
>> such file or directory [   15.407958] systemd[1354]: Failed at step EXEC
>> spawning /bin/plymouth: No such file or directory [   15.924438]
>> systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   16.170410] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   16.219970] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   17.234588] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   17.305603] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   17.365386] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   17.403839] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   17.424804] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   17.446258] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.150482] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.311523] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.372406] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.423492] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.481750] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.507293] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.531219] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.547668] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.569580] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.599334] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.854309] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.881835] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.898162] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.915344] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   24.931701] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   25.384979] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   25.543670] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   59.930755] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   67.187499] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   67.202758] systemd[1]: Starting Journal Service...
>> [   67.210510] systemd-journald[939]: Failed to rotate
>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No such
>> file or directory [   67.226593] systemd-journald[939]: Received SIGTERM
>> from PID 1 (systemd). [   67.237731] systemd-journald[939]: Failed to
>> rotate /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal: No
>> such file or directory [   67.283477] systemd[1]: Unit
>> systemd-journald.service entered failed state. [   67.301147] systemd[1]:
>> systemd-journald.service has no holdoff time, scheduling restart. [  
>> 67.311065] systemd[1]: Stopping Journal Service...
>> [   67.317718] systemd[1]: Starting Journal Service...
>> [   67.344177] systemd[1]: Started Journal Service.
>> [   67.365356] systemd[1]: Starting Trigger Flushing of Journal to
>> Persistent Storage... [   67.485595] systemd[1]:
>> systemd-journal-flush.service: main process exited, code=exited,
>> status=1/FAILURE [   67.526092] systemd[1]: Failed to start Trigger
>> Flushing of Journal to Persistent Storage.
>> 
>> The last handful of lines repeats every 30 seconds.
>> 
>> It is even impossible to debug that:
>> 
>> root at gta04:~# systemctl --state=failed
>> Failed to get D-Bus connection: Unknown error -1
>> root at gta04:~#
>> 
>> Is someone already using systemd? And/or has experience in administration?
> 
> 
> Systems wants to write its log data to /run/log/journal, which doesn’t exist.

The strange thing is that the file (and directory)

>> /run/log/journal/f3be05d3555146cfaf346d194a08336d/system.journal

exists…

> 
> Try setting “Storage" in /etc/systemd/journald.conf to "none".

This might silence the problem but maybe not really solve it.
At least I would assume that on Debian (almost stable) it must
work out of the box without fixing something.

BR,
Nikolaus