[SOLVED] Systemd journal not preserved through reboot

It appears that my journal in /var/log/journal is being flushed just before reboot. Every time I view the journal with the --all flag, the furthest back I can go is to right before the last reboot or power-off. Moreover, my /var/log/journal directory seems incapable of growing bigger than 2.6Mb or so, even though I have the journal configured to max out at 50Mb.
Here's my /etc/journald.conf:
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See journald.conf(5) for details
[Journal]
Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=login
#SyncIntervalSec=5m
#RateLimitInterval=10s
#RateLimitBurst=200
SystemMaxUse=50M
#SystemKeepFree=
#SystemMaxFileSize=
#RuntimeMaxUse=500M
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=yes
#ForwardToKMsg=no
#ForwardToConsole=no
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
Any ideas?
Last edited by nbtrap (2013-07-01 10:10:47)

Also of free space and that will trump SystemMaxUse. I know because it happens on my system. As /var fills, systemd keeps smaller persistent journal records.
EDIT:
SystemMaxUse= and RuntimeMaxUse= control how much disk space the
journal may use up at maximum. Defaults to 10% of the size of the respective file system. SystemKeepFree= and
RuntimeKeepFree= control how much disk space the journal shall always leave free for other uses if less than the disk space
configured in SystemMaxUse= and RuntimeMaxUse= is available. Defaults to 15% of the size of the respective file system.
SystemMaxFileSize= and RuntimeMaxFileSize= control how large individual journal files may grow at maximum.
Strictly speaking this seems inaccurate, though. You have more than the value of SystemMaxUse available so SystemKeepFree should not apply. However, it does.
Last edited by cfr (2013-07-01 02:41:22)

Similar Messages

[Solved] Systemd journal in conjunction with syslog-ng?

The wiki has this item:
https://wiki.archlinux.org/index.php/Sy … log_daemon
I'm just wondering what that is all about. Is that for causing systemd to be the source of syslog log entries rather than syslog?
I don't really see the point of this, and don't want to be double-logging everything. I'm happy with the systemd journal (for now). Should I just shut down syslog-ng? I assume the command is "systemctl disable syslog-ng.service"?
Last edited by PaulBx1 (2012-08-30 07:14:39)

Did you make sure syslog does not show up in your rc.conf "daemons" array? That was what was screwing me up. You can tell if syslog is still operating by doing a "systemctl list-units".
This is my conf file:
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See journald.conf(5) for details
[Journal]
#Compress=yes
#RateLimitInterval=10s
#RateLimitBurst=200
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMinFileSize=
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMinFileSize=
#ForwardToSyslog=yes
#ForwardToKMsg=no
#ForwardToConsole=no
#ImportKernel=no
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#Storage=auto
Last edited by PaulBx1 (2012-08-30 20:35:16)

[solved] systemd-journal and shadow.pacnew updates

After a recent install and update I have come across the same issue described here where the user was recommended to ignore and erase some .pacnew files. My update generated the following:
/etc/dhcpcd.conf.pacnew
/etc/group.pacnew
/etc/passwd.pacnew
/etc/shadow.pacnew
/etc/gshadow.pacnew
The first, dhcpcd, seemed sensible enough and I incorporated the changes. The latter four all share the following characteristics:
1. Removed mentions of systemd-journal-remote and systemd-journal-upload. I'm not sure why so I left those records in place.
2. Changed a few permissions here or there, which i incorporated into /etc/group and /etc/password.
3. Changed the default shell for a few users; these changes I incorporated.
I was unable to open /etc/shadow or /etc/gshadow in write mode so I've left these files. Perhaps that's fine because the thread mentioned above says so. However, there's no explanation of why or where this information was obtained (or ordained!)
Is it fine to leave these two files? Why have syssystemd-journal-remote and systemd-journal-upload been omitted?
Last edited by Deau (2014-08-29 06:54:18)

The steps you took look quite sane to me.
These groups are not in the defaults provided by filesystem (e.g. I don't have them). see the edit
Apparently systemd creates system groups and users on it's own, see 'man systemd-sysusers'. Do you know / can figure out why these groups are created in the first place ? not important in this case, see the edit as well
FYI e.g.: https://bugs.archlinux.org/task/41717
The filesystem package provides those files as defaults (group, passwd, shadow, gshadow amongst otheres). However there are some packages that actually add additional groups they need (like ntp e.g.). The filesystem package cannot know about these. Therefor it's likely to have more groups in your local installation than in the .pacnew files you get.
The same applies for manually created users and groups of course.
If needed see the man pages for explanations of the respective files (e.g. 'man group').
Edit: Ok, I see that after an update I have them as well, so these are apparently new systemd groups and users. I think the rest I said above is still valid, so leaving those in place was the right thing to do.
Last edited by rebootl (2014-08-28 20:46:43)

[SOLVED] systemd service not starting

Hi,
Been using Arch for just over a week now moving from Ubuntu and loving it. Achieved so much more on Arch in this short time until this evening.
I am trying to run a shell script at startup. I added the service file under /etc/systemd/system/myapp.service
With the following content:
[Unit]
Description=Notification
[Service]
ExecStart=/usr/bin/myscript
[Install]
WantedBy=multi-user.target
As it is I can run "systemctl restart myapp.service" and the script execute flawlessly however on reboot it does nothing and I get this error when I run systemctl status myapp.service:
systemctl status myapp.service
myapp.service - Notification
Loaded: loaded (/etc/systemd/system/myapp.service; enabled)
Active: failed (Result: exit-code) since Thu 1970-01-01 10:00:08 EST; 14s ago
Process: 116 ExecStart=/usr/bin/myscript (code=exited, status=6)
Other info:
Script starts with #!/bin/sh
Script permissions 755
Tried adding After=network.target under unit.
Tried Type=oneshot and forking
O yes /var/log/messages.log | grep myapp
Sep 6 14:25:56 alarm systemd[1]: [/etc/systemd/system/myapp.service:1] Unknown section 'unit'. Ignoring.
Sep 6 14:25:56 alarm systemd[1]: [/etc/systemd/system/myapp.service:2] Assignment outside of section. Ignoring.
Jan 1 01:00:11 alarm systemd[1]: myapp.service: main process exited, code=exited, status=6/NOTCONFIGURED
Jan 1 01:00:11 alarm systemd[1]: Unit myapp.service entered failed state.
Jan 1 01:00:11 alarm [ 3.243318] systemd[1]: [/etc/systemd/system/myapp.service:1] Unknown section 'unit'. Ignoring.
Jan 1 01:00:11 alarm [ 3.243490] systemd[1]: [/etc/systemd/system/myapp.service:2] Assignment outside of section. Ignoring.
Only thing I dont get is the date difference? I have set the timezone correctly..
Any suggestions?
thanks
Last edited by blueteq (2013-09-10 10:01:11)

Reaching the network.target does not necessarily mean that an active connection has been reached. For example, if you use wicd or netctl-auto, it will report the stating of the service as successful after the daemon itself has started, but starting the daemon simply means that it is ready to start scanning for wireless networks and then connect.
If you want to be absolutely sure that there is a network connection before the service starts, you should use NetworkManager.service. That will also pull in the NetworkManager-wait-online.service which will not complete until a full connection has been reached. At that point the startup will have reached the network-online.target. So you should order the service after that instead. In reality, you should order it after that anyway, no matter what netowrk connection service you use, as that is a built in target to systemd.
Even though you have the RestartSec=35 and Restart=on-failure (which is a sane thing to do IMO), it is probably a good idea to order it After=netowrk-online.target anyway, as that will cause the service to start a bit later and at least attempt to order itself correctly. That way it will also ensure that the service is stopped before the network is taken down as well, hopefully ensuring a clean disconnect as well.

[solved] systemd services not starting at boot (or at all)

On my router, some systemd services fail to start at boot.
The services are :
adsl (pppoe connetction on the wan interface)
shorewall (funny again for a router)
logind (brings up only tty1, and not the others with a 'timeout' error)
adsl starts fine manually after booting up
the others don't work, I have to launch shorewall with the old sysvinit rc script (and it works)
I really don't know, what happened to logind...
Last edited by scar (2012-11-30 10:20:44)

cups: avahi client failed
adsl: timeout (ppp0 running on eth0, the service did not found eth0)
shorewall: did not work by the systemctl command, only with the old rc script
I'm not sure if there was an error with logind, but I've had only tty1, not all the others (I have not touched /etc/inittab)
since this was a very old install (but up to date), I've decided to reinstall the whole thing,
Everything works
(But reinstalling does not solve any problem, it erases the problems...)
Last edited by scar (2012-11-30 10:21:20)

Solaris 10 zones - Resource Controls not persisting through reboot

Local zone was rebooted, but somehow the resource controls are not well configured and the oracle database did not start up.
The cat /etc/project shows this : The local zone has 10 gb. The oracle database was started manually with the startdb.sh, which conn /assysdba and issue a startup, adn also startups the listener.
cat /etc/project
system:0::::project.max-shm-memory=(privileged,8589934000,deny)
user.root:1::::project.max-shm-memory=(privileged,8589934000,deny)
noproject:2::::
default:3::::project.max-shm-memory=(privileged,6442450944,deny)
group.staff:10::::
user.oracle:100::oracle::project.max-shm-memory=(privileged,8589934000,deny)
group.dba:101::::project.max-sem-ids=(privileged,100,deny);project.max-shm-ids=(
privileged,100,deny);project.max-shm-memory=(privileged,6442450944,deny)

Nikolay, thank you for your reply.
What I know is that the zone was rebooted saturday. sunady at 1:00 am the oracle database (I'am a Dba not sysadmin), perform coldbackup (veritas.) then Veritas call a unix script to starts the database.
I run the script to starts the database manually sunday. Veritas could not open the database because of the Out of Memory.
The box has 10 gb , the oracle user, the rot and system are configured to use 8 gb, the rest are configured to use less.
I'am oracle user.
id -p
uid=100(oracle) gid=100(dba) projid=100(user.oracle)
prctl -i process $$
process: 8928: -ksh
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
process.max-port-events
privileged 65.5K - deny -
system 2.15G max deny -
process.max-msg-messages
privileged 8.19K - deny -
system 4.29G max deny -
process.max-msg-qbytes
privileged 64.0KB - deny -
system 16.0EB max deny -
process.max-sem-ops
privileged 512 - deny -
system 2.15G max deny -
process.max-sem-nsems
privileged 512 - deny -
system 32.8K max deny -
process.max-address-space
privileged 16.0EB max deny -
system 16.0EB max deny -
process.max-file-descriptor
basic 256 - deny 8928
privileged 65.5K - deny -
system 2.15G max deny -
process.max-core-size
privileged 8.00EB max deny -
system 8.00EB max deny -
process.max-stack-size
basic 8.00MB - deny 8928
privileged 8.00EB - deny -
system 8.00EB max deny -
process.max-data-size
privileged 16.0EB max deny -
system 16.0EB max deny -
process.max-file-size
privileged 8.00EB max deny,signal=XFSZ -
system 8.00EB max deny -
process.max-cpu-time
privileged 18.4Es inf signal=XCPU -
system 18.4Es inf none -
task.max-cpu-time
system 18.4Es inf none -
task.max-lwps
system 2.15G max deny -
project.max-contracts
privileged 10.0K - deny -
project.max-device-locked-memory
privileged 987MB - deny -
project.max-locked-memory
system 16.0EB max deny -
project.max-port-ids
privileged 8.19K - deny -
project.max-shm-memory
privileged 8.00GB - deny -
project.max-shm-ids
privileged 128 - deny -
project.max-msg-ids
privileged 128 - deny -
project.max-sem-ids
privileged 128 - deny -
project.max-crypto-memory
privileged 3.85GB - deny -
project.max-tasks
system 2.15G max deny -
project.max-lwps
system 2.15G max deny -
project.cpu-cap
system 4.29G inf deny -
project.cpu-shares
privileged 1 - none -
zone.max-swap
privileged 20.0GB - deny -
zone.max-locked-memory
system 16.0EB max deny -
zone.max-shm-memory
system 16.0EB max deny -
zone.max-shm-ids
system 16.8M max deny -
zone.max-sem-ids
system 16.8M max deny -
zone.max-msg-ids
system 16.8M max deny -
zone.max-lwps
system 2.15G max deny -
zone.cpu-cap
system 4.29G inf deny -
zone.cpu-shares
privileged 1 - none -
Print configured reso
urce control
ksh: Print: not found

[SOLVED] Console Font Not Retained After Reboot

Hi, again. Happy to report that I successfully installed Arch Linux last night, with no problems whatsoever. Thanks to those who addressed my concerns. Still reading up on the package manager, user and group management, etc.
Anyway, one of the first things I noticed is that the console font gets reset after every reboot. I need to manually type "setfont Lat2-Terminus16" - which works just fine, except for the annoyance in having to do that each time I boot up. My /etc/vconsole.conf has the following:
KEYMAP=us
FONT=Lat2-Terminus16
Following the solution described here:
https://bbs.archlinux.org/viewtopic.php?id=155876
I added 'consolefont' (without quotes) to the beginning (first item) of the HOOKS line in /etc/mkinitcpio.conf. Then I rebuilt the initramfs by typing "mkinitcpio -p linux". Again, no errors during the rebuild.
I've rebooted several times, but there's no change... my selected console font is not retained.
Can anyone point what I'm doing wrong, or offer ideas? Thanks.
Last edited by R0b0ty (2013-03-06 16:52:42)

Have you tried
If the fonts seems to not change on boot, or change only temporarily, it is most likely that they got reset when graphics driver was initialized and console was switched to framebuffer. To avoid this, load your graphics driver earlier. See for example KMS#Early_KMS_start or other ways to setup your framebuffer before /etc/vconsole.conf gets applied.
https://wiki.archlinux.org/index.php/Fonts#Examples_2

[Solved] systemd does not wait for the unit to finish

My problem is described in the title. I have made a test by enabling the following unit:
[Unit]
Description=/etc/rc.local Compatibility
[Service]
Type=forking
ExecStart=/bin/sleep 1000
TimeoutSec=0
RemainAfterExit=yes
After=network.target
[Install]
WantedBy=multi-user.target
The unit is well started (a process sleep 1000 exists). But with a type=forking, systemd is supposed to hang in this case. Instead, the graphical.target is launched, systemctl list-units mention it as dead, but the display manager is started before the sleep 1000 completes. Ho can I force systemd to wait?
Last edited by olive (2015-03-16 16:49:34)

olive, now you're making even less sense. I didn't say the sleep example was stupid and I didn't question your reasons for doing/wanting this.
I suggested you add "Before=display-manager.service" and you respond "I added Before=graphical.target and it didn't change anything."
I also tried to explain why systemd has no reason to delay the display-manager.service. You could have asked for further clarification, as berbae has now done. Let's try a longer explanation.
Service startup
Services can be started in different ways, as configured with Type=. This determines when a service is considered "started" (or when the service's start-up is considered finished). When a service reaches this state (some time after being started), units that are supposed to start After= this service will be started (and no sooner).
With simple systemd has no further information about the start-up process. It launches whatever you specify in ExecStart and this is the main process that continues to run till the service stops. systemd assumes this type of service is started immediately. All the other types have some way for the process to indicate to systemd (either directly or indirectly) when it has finished starting.
Actually oneshot is also a bit special and that is where RemainAfterExit comes in. For oneshot, systemd waits for the process to exit before it starts any follow-up units (and with multiple ExecStarts I assume it waits for all of them). So that automatically leads to the scheme in berbae's last post. However, with RemainAfterExit, the unit remains active even though the process has exited, so this makes it look more like "normal" service with
begin of unit/startup ---- end of startup ------ end of unit
This is the relevant behavior for this thread. First sleep starts, then after 1000 seconds, start-up finishes and follow-up units will be started. Then either the unit dies, or (with RemainAfterExit) it stays "active".
The man page describes how "end of startup" is determined for each Type.
Targets
Targets are meant to group units together, to provide synchronization points (and replace runlevels). When you start a target, all its units will be started (in parallel if possible). The man page says:
Unless DefaultDependencies= is set to false, target units will
implicitly complement all configured dependencies of type Wants=,
Requires=, RequiresOverridable= with dependencies of type After= if the
units in question also have DefaultDependencies=true.
This means that (by default) when a target is requested, all it units are started first. Only after all units have finished starting, the target itself will be started (and since the target doesn't do anything by itself, this startup is basically instantaneous). Without this dependency, the order between the target and its units is unspecified, so in theory the target could finish starting immediately while its units are still being started.
Back to olive
graphical.target has these DefaultDependencies, so it is not started until all its units (like display-manager.service) and other After= dependencies (like multi-user.target) have finished starting. Your sleep service has to be started before multi-user.target starts (again due to default target dependencies). So first display-manager and the sleep service are started and after 1000 seconds, the sleep service finishes starting and then (assuming all other dependencies were quicker) multi-user.target is started and graphical.target as well (assuming display-manager didn't need 1000 seconds).
If you want display-manager.service after the sleep service, add a Before/After line to specify that (this was your original goal and my suggestion).
olive wrote wrote:However, units that are parts of the graphical target are still launched before the graphical target become active. I am still unable to completely delay the starts of the graphical target before a specific unit completes.
It should be clear now how this works. "units that are part of the graphical target" can only mean "units that are wanted/required by the graphical target" but that is basically all the units that are started when you boot your system, because multi-user.target is a part of graphical.target. And your sleep service is a part of multi-user.target, so in fact you're saying you want to delay starting the sleep service until the sleep service completes
What you probably intended was to delay all units that are a part of graphical.target but not of multi-user.target until after the sleep service. I can't think of an easy (or even good) way to do this and this post is already too long, so I'll table that for now.

Sound settings not sticking through reboot after 10.6.2

Since 10.6.2, my sound preferences are not sticking and always default to "internal speakers" on my MacPro1,1. I tried running the combo updater without success. Any other ideas?
Thanks.

check another forum topic for potential answer:
http://discussions.apple.com/thread.jspa?threadID=2160114&tstart=0
I had the same problem and fixed mine. Others have fixed theirs too trying different methods discussed there.
Good luck.

[solved]systemd can not auto start tomcat7.service

Because the boot spend too much time. in tomcat7.servce,line 21: wait=10 \
change to wait=50 \ or more big number.then the service can start success.

Because the boot spend too much time. in tomcat7.servce,line 21: wait=10 \
change to wait=50 \ or more big number.then the service can start success.

[SOLVED] systemd, systemd-journal constantly at high CPU %age

Hi all,
I've switched a computer to systemd, and everything works nicely. The system is responsive and booting is even faster than before. Yay!
However, both my CPU cores are constantly between 80% and 90%. When I do top in a terminal, I see systemd constantly in the 90%-100% range and systemd-journal in the 60%-100% range, also continuously. My CPU temperature is a lot higher than normal as well (currently at 61.0C)
Is this normal?
Last edited by diederick76 (2012-09-13 06:03:11)

I'm having a similar problem. I temporarily fixed it by replacing the cupsd.conf with the cupsd.con.default. Everything ran great, got the printer configured again, journald stopped thrashing my precious SSD by producing millions of these warnings (I didn't wc them, but I was probably getting thousands every second) and all was well. Until I "shared" the printer again. Immediately cupsd got locked into restarting thousands of times every second, once again thrashing my cpu and SSD.
Edit:
I guess I should probably share my cupsd.conf. I didn't manually edit it, I used the web interface:
cat /etc/cups/cupsd.conf
LogLevel warn
SystemGroup sys root
# Allow remote access
Port 631
Listen /var/run/cups/cups.sock
# Share local printers on the local network.
Browsing On
BrowseLocalProtocols dnssd
DefaultAuthType Basic
WebInterface Yes
<Location />
# Allow shared printing...
Order allow,deny
Allow all
</Location>
<Location /admin>
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
</Location>
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy authenticated>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
Edit02:
I should mention that I tried the fix described here: https://bbs.archlinux.org/viewtopic.php?id=146154
Deiderick: Have you "shared" your printer? I suspect that this may be what is causing the problem.
To Mods: At this point, because the OP's problem has been resolved, and this thread is marked "solved" should I make a new thread? It is possible that my problem is not identical to the OP's.
As a side note, I ran "journalctl | wc -l" it took about a minute of maxing out one core to finish. The final number: 1232889. I have a feeling that this reflects only a fraction of the warnings that cups produced, seeing as I only allocated limited hd space for journal messages.
Edit03: After re-reading the etiquette thread, I've decided to start a new thread. This one is marked "solved" and although very similar, it may not be exactly the same problem that I am having.
Last edited by Convergence (2012-09-23 00:28:14)

Systemd poweroff not working [SOLVED]

I have installed systemd on both my laptop and my desktop pc. The laptop is working fine, but the desktop PC will not poweroff any more.
systemctl reboot, halt or poweroff simply run to "Stopped target Remote File Systems" and then sits winking at me.
Adding --force just gets to the winking quicker.
To be honest, I don't know where to look.
Thanks
Andrew
arch x86_64 up to date
Last edited by fdservices (2013-02-14 15:49:23)

Here is the journal from my last shutdown:
Oct 30 15:54:40 ezcool login[432]: ROOT LOGIN ON tty1
Oct 30 15:54:44 ezcool systemd-logind[428]: Removed session 1.
Oct 30 15:55:01 ezcool /usr/sbin/crond[1326]: pam_unix(crond:session): session opened for user root by (uid=0)
Oct 30 15:55:01 ezcool /USR/SBIN/CROND[1327]: (root) CMD (scanimage -n)
Oct 30 15:55:02 ezcool /USR/SBIN/CROND[1326]: (root) CMDOUT (sh: /sbin/ifconfig: No such file or directory)
Oct 30 15:55:02 ezcool /USR/SBIN/CROND[1338]: (CRON) EXEC FAILED (/usr/sbin/sendmail): No such file or directory
Oct 30 15:55:05 ezcool systemd[1]: Deactivating swap /dev/sda5...
Oct 30 15:55:05 ezcool systemd[1]: Deactivating swap /dev/sda5...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Bluetooth.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Bluetooth.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Sound Card.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Sound Card.
Oct 30 15:55:05 ezcool systemd[1]: Stopping RPC Port Mapper.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target RPC Port Mapper.
Oct 30 15:55:05 ezcool systemd[1]: Stopping clamav updater...
Oct 30 15:55:05 ezcool systemd[1]: Stopping clamav daemon...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Dynamic DNS Update Client...
Oct 30 15:55:05 ezcool systemd[1]: Stopping UDisks...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Daemon for power management...
Oct 30 15:55:05 ezcool systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Console Manager...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Daemon for monitoring attached scanners and registering them with colord...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Oct 30 15:55:05 ezcool systemd[1]: Stopping CUPS Printing Service...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Graphical Interface.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Graphical Interface.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Multi-User.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Multi-User.
Oct 30 15:55:05 ezcool systemd[1]: Stopping NFSv4 ID-name mapping daemon...
Oct 30 15:55:05 ezcool systemd[1]: Stopping NFS Mount Daemon...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Periodic Command Scheduler...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Network Time Service...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Samba SMB/CIFS server...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Samba Winbind daemon...
Oct 30 15:55:05 ezcool rpc.mountd[626]: Caught signal 15, un-registering and exiting.
Oct 30 15:55:05 ezcool avahi-daemon[422]: Got SIGTERM, quitting.
Oct 30 15:55:05 ezcool avahi-daemon[422]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.100.5.
Oct 30 15:55:05 ezcool winbindd[584]: [2012/10/30 15:55:05.500858, 0] winbindd/winbindd.c:212(winbindd_sig_term_handler)
Oct 30 15:55:05 ezcool winbindd[584]: Got sig[15] terminate (is_parent=1)
Oct 30 15:55:05 ezcool avahi-daemon[422]: avahi-daemon 0.6.31 exiting.
Oct 30 15:55:05 ezcool sshd[424]: Received signal 15; terminating.
Oct 30 15:55:05 ezcool NetworkManager[421]: <warn> disconnected by the system bus.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Samba NetBIOS name server...
Oct 30 15:55:05 ezcool systemd[1]: Stopping OpenSSH Daemon...
Oct 30 15:55:05 ezcool systemd[1]: Stopping D-Bus System Message Bus...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Arch Daemons.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Arch Daemons.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Login Service...
Oct 30 15:55:05 ezcool systemd[1]: Stopping Login Prompts.
Oct 30 15:55:05 ezcool systemd[1]: Stopped target Login Prompts.
Oct 30 15:55:05 ezcool systemd[1]: Stopping Getty on tty1...
Oct 30 15:55:05 ezcool systemd[1]: Stopping K Display Manager...
Oct 30 15:55:05 ezcool systemd[1]: Starting Store Sound Card State...
Oct 30 15:55:05 ezcool systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Oct 30 15:55:05 ezcool NetworkManager[421]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on
Oct 30 15:55:05 ezcool kdm[1296]: :0[1296]: Abnormal termination of greeter for display :0, code 0, signal 11
Oct 30 15:55:05 ezcool systemd[1]: Stopped OpenSSH Daemon.
Oct 30 15:55:05 ezcool systemd[1]: Stopped D-Bus System Message Bus.
Oct 30 15:55:05 ezcool systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Oct 30 15:55:05 ezcool login[432]: pam_unix(login:session): session closed for user root
Oct 30 15:55:05 ezcool systemd[1]: Stopped Login Service.
Oct 30 15:55:05 ezcool systemd[1]: Unit systemd-logind.service entered failed state
Oct 30 15:55:05 ezcool systemd[1]: Stopped K Display Manager.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Manage, Install and Generate Color Profiles.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Console Manager.
Oct 30 15:55:05 ezcool systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Samba SMB/CIFS server.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Samba Winbind daemon.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Samba NetBIOS name server.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Network Time Service.
Oct 30 15:55:05 ezcool systemd[1]: rpc-mountd.service: main process exited, code=exited, status=1/FAILURE
Oct 30 15:55:05 ezcool systemd[1]: Stopped NFS Mount Daemon.
Oct 30 15:55:05 ezcool systemd[1]: Unit rpc-mountd.service entered failed state
Oct 30 15:55:05 ezcool systemd[1]: Stopped NFSv4 ID-name mapping daemon.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Daemon for power management.
Oct 30 15:55:05 ezcool systemd[1]: Stopped UDisks.
Oct 30 15:55:05 ezcool systemd[1]: Stopped Dynamic DNS Update Client.
Oct 30 15:55:05 ezcool systemd[1]: freshclamd.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 30 15:55:05 ezcool systemd[1]: Stopped clamav updater.
Oct 30 15:55:05 ezcool systemd[1]: Unit freshclamd.service entered failed state
Oct 30 15:55:05 ezcool systemd[1]: Stopped clamav daemon.
Oct 30 15:55:05 ezcool systemd[1]: Deactivated swap /dev/sda5.
Oct 30 15:55:06 ezcool systemd[1]: Started Store Sound Card State.
Oct 30 15:55:06 ezcool systemd[1]: Unmounting RPC pipe filesystem...
Oct 30 15:55:06 ezcool systemd[1]: Stopping NFS server...
Oct 30 15:55:06 ezcool systemd[1]: Deactivated swap /dev/disk/by-uuid/b134f334-2434-456d-9b29-1551b70a7e04.
Oct 30 15:55:06 ezcool kernel: nfsd: last server has exited, flushing export cache
Oct 30 15:55:06 ezcool systemd[1]: Deactivated swap /dev/disk/by-id/ata-MAXTOR_STM380215AS_6QZ11948-part5.
Oct 30 15:55:06 ezcool systemd[1]: Stopped CUPS Printing Service.
Oct 30 15:55:06 ezcool systemd[1]: Unmounted RPC pipe filesystem.
Oct 30 15:55:06 ezcool systemd[1]: Stopped NFS server.
Oct 30 15:55:06 ezcool systemd[1]: Stopping RPC Bind...
Oct 30 15:55:06 ezcool rpcbind[586]: rpcbind terminating on signal. Restart with "rpcbind -w"
Oct 30 15:55:06 ezcool login[432]: pam_systemd(login:session): Failed to connect to system bus: Did not receive a reply. Possible causes include: th
Oct 30 15:55:06 ezcool systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 30 15:55:06 ezcool systemd[1]: Stopped RPC Bind.
Oct 30 15:55:06 ezcool systemd[1]: Unit rpcbind.service entered failed state
Oct 30 15:55:06 ezcool systemd[1]: Stopped Getty on tty1.
Oct 30 15:55:06 ezcool systemd[1]: Stopping /etc/rc.local Compatibility...
Oct 30 15:55:06 ezcool systemd[1]: Stopped /etc/rc.local Compatibility.
Oct 30 15:55:06 ezcool systemd[1]: Stopping Permit User Sessions...
Oct 30 15:55:06 ezcool systemd[1]: Stopping Network.
Oct 30 15:55:06 ezcool systemd[1]: Stopped target Network.
Oct 30 15:55:06 ezcool systemd[1]: Stopping Network Manager...
Oct 30 15:55:06 ezcool NetworkManager[421]: <info> caught signal 15, shutting down normally.
Oct 30 15:55:06 ezcool dhcpcd[453]: received SIGTERM, stopping
Oct 30 15:55:06 ezcool dhcpcd[453]: eth0: removing interface
Oct 30 15:55:06 ezcool NetworkManager[421]: <info> exiting (success)
Oct 30 15:55:06 ezcool systemd[1]: Stopped Network Manager.
Oct 30 15:55:06 ezcool systemd[1]: Stopped Permit User Sessions.
Oct 30 15:55:06 ezcool systemd[1]: Stopping Remote File Systems.
Oct 30 15:55:06 ezcool systemd[1]: Stopped target Remote File Systems.
Oct 30 15:56:35 ezcool systemd[1]: colord-sane.service stopping timed out. Killing.
Oct 30 15:58:05 ezcool systemd[1]: colord-sane.service still around after SIGKILL. Ignoring.
Oct 30 15:59:35 ezcool systemd[1]: colord-sane.service stopping timed out (2). Killing.
Oct 30 16:01:05 ezcool systemd[1]: colord-sane.service still around after SIGKILL (2). Entering failed mode.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Daemon for monitoring attached scanners and registering them with colord.
Oct 30 16:01:05 ezcool systemd[1]: Unit colord-sane.service entered failed state
Oct 30 16:01:05 ezcool systemd[1]: Stopping Basic System.
Oct 30 16:01:05 ezcool systemd[1]: Stopped target Basic System.
Oct 30 16:01:05 ezcool systemd[1]: Starting /etc/rc.local.shutdown Compatibility...
Oct 30 16:01:05 ezcool systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Oct 30 16:01:05 ezcool systemd[1]: Stopping CUPS Printer Service Spool.
Oct 30 16:01:05 ezcool systemd[1]: Stopped CUPS Printer Service Spool.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Daily Cleanup of Temporary Directories.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Sockets.
Oct 30 16:01:05 ezcool systemd[1]: Stopped target Sockets.
Oct 30 16:01:05 ezcool systemd[1]: Stopping CUPS Printing Service Sockets.
Oct 30 16:01:05 ezcool systemd[1]: Closed CUPS Printing Service Sockets.
Oct 30 16:01:05 ezcool systemd[1]: Closed D-Bus System Message Bus Socket.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Load Kernel Modules...
Oct 30 16:01:05 ezcool systemd[1]: Stopped Load Kernel Modules.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Apply Kernel Variables.
Oct 30 16:01:05 ezcool systemd[1]: Stopped Setup Virtual Console.
Oct 30 16:01:05 ezcool systemd[1]: Unmounting /tmp...
Oct 30 16:01:05 ezcool systemd[1]: Started /etc/rc.local.shutdown Compatibility.
Oct 30 16:01:05 ezcool systemd[1]: Started Console System Shutdown Logging.
Oct 30 16:01:05 ezcool systemd[1]: Unmounted /tmp.
Oct 30 16:01:05 ezcool systemd[1]: Unmounted /home.
Oct 30 16:01:05 ezcool systemd[1]: Starting Unmount All Filesystems.
Oct 30 16:01:05 ezcool systemd[1]: Reached target Unmount All Filesystems.
Oct 30 16:01:05 ezcool systemd[1]: Stopping Local File Systems (Pre).
Oct 30 16:01:05 ezcool systemd[1]: Stopped target Local File Systems (Pre).
Oct 30 16:01:05 ezcool systemd[1]: Stopping Remount Root and Kernel File Systems...
Oct 30 16:01:05 ezcool systemd[1]: Stopped Remount Root and Kernel File Systems.
Oct 30 16:01:05 ezcool systemd[1]: Starting Shutdown.
Oct 30 16:01:05 ezcool systemd[1]: Reached target Shutdown.
Oct 30 16:01:05 ezcool systemd[1]: Starting Update UTMP about System Shutdown...
Oct 30 16:01:05 ezcool systemd[1]: Starting Save Random Seed...
Oct 30 16:01:05 ezcool systemd[1]: Started Update UTMP about System Shutdown.
Oct 30 16:01:05 ezcool systemd[1]: Started Save Random Seed.
Oct 30 16:01:05 ezcool systemd[1]: Starting Final Step.
Oct 30 16:01:05 ezcool systemd[1]: Reached target Final Step.
Oct 30 16:01:05 ezcool systemd[1]: Starting Power-Off...
Oct 30 16:01:05 ezcool systemd[1]: Shutting down.
Oct 30 16:01:05 ezcool systemd-journal[153]: Journal stopped
but it lies, the final messages to the terminal were:
Disabling Swaps
Detaching Loop Devices
Detaching DM Devices
it did not power down or shut down.
Andrew

[SOLVED] netcfg static IP not persisting across reboots in VM

I ran into an issue with netcfg static IP not persisting across reboots in a VM. I figured it out, but it took me awhile as a brand new user, so I thought I'd post it.
Setup
Using VMWare Workstation 8.0.3 build-703057 with bridged networking
Host OS: Linux Mint 14 64-bit
Guest OS: Arch Linux 2013.03.01 x86_64
Given a fresh install on the guest, setup netcfg:
cd /etc/network.d
cp examples/ethernet-static ./myprofile
nano myprofile
# customize this file. I also added NETMASK='255.255.255.0'
systemctl enable netcfg@myprofile
systemctl start netcfg@myprofile
Test the configuration. It should be successful:
ping google.com
Problem
See if the changes survive a reboot.
reboot
ping google.com
I got the error "connect: Network is unreachable".
Check the logs:
journalctl
G
I found the following netcfg failure..
[email protected]: main process exited, code=exited, status=1/FAILURE
..prior to the following device initialization:
kernel: e1000 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection
system-udevd[117]: renamed network interface eth0 to emp2s0
Solution
It looks like netcfg is being started before the device it depends on has been initialized. Inform systemd of the
dependency so they start in the proper order:
# nano /etc/systemd/system/multi-user.target.wants/[email protected]
# Add the following to [Unit]. Remember to replace enp2s0 with your device name.
Requires=sys-subsystem-net-devices-enp2s0.device
After=sys-subsystem-net-devices-enp2s0.device
Test again:
reboot
ping google.com
This should now be successful.

fukawi2 wrote:
$ man netcfg-profiles wrote:
Miscellaneous options
IPCFG
Array of arguments to pass to ip. The power of this options is
that it allows both simple and complicated routing
configurations, within the framework of netcfg.
SKIPNOCARRIER
‘yes’/‘no’. Don’t abort interface setup if no carrier is
found.
Thank you, [Solved].

Can't get my Ipad to charge through the PC or wall adapter, it's stuck on the connect to Itunes screen and will not let me reboot it.

My Ipad has been stuck on the connect to Itunes screen now for days, it will not charge through the PC or wall charger. When plugged into the PC it is not recognized by it. Itunes doesn't see it and it will not let me reboot the system. How can I get past this so I can start using it again?

Hello Aloe_85,
This screen indicates that your device must be restored before it can be used again. The steps detailed in the article below can help get your iPad to reappear in iTunes so that it may be restored.
iOS: Device not recognized in iTunes for Windows
http://support.apple.com/kb/TS1538
Cheers,
Allen

Systemd-journal process using 100% of one cpu core after reboot

journalctl -b showed
"Process 2016 (virtuoso-t) dumped core."
more than a few times and virtuoso-t would was using more cpu than it does most of the time.
at 14 minutes of uptime systemd-journal stopped using 100% and went back to normal. Anyone know a way to figure out what happened here?
update:
systemd-coredump[3182]: Process 3133 (virtuoso-t) dumped core.
systemd-journal[5407]: Permanent journal is using 2.6G (max allowed 4.0G, trying to leave 4.0G free of 50.7G available → current limit 4.0G).
systemd[1]: systemd-journald.service watchdog timeout!
systemd[1]: Starting Journal Service...
systemd[1]: systemd-journald.service stop-sigterm timed out. Killing.
systemd[1]: Starting Journal Service...
systemd[1]: systemd-journald.service: main process exited, code=killed, status=9/KILL
systemd[1]: Unit systemd-journald.service entered failed state.
systemd[1]: systemd-journald.service has no holdoff time, scheduling restart.
systemd[1]: Stopping Journal Service...
systemd[1]: Starting Journal Service...
systemd[1]: Started Journal Service.
systemd-journal[5407]: Journal started
dbus[365]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
dbus[365]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No such file or directory.
systemd-coredump[3289]: Process 3235 (virtuoso-t) dumped core.
it happened again here is what the journal was saying while it was happening (i removed lots of (virtuoso-t) dumped core that happened ... 10 or more times)
Thanks in advance,
Wolf Larson
Last edited by wolflarson (2014-03-22 15:36:37)

In the Newbie Corner of the forums, there are a few stickied threads that are recommended reads. One of which is this one.
If the logs are not too too much, then it can be posted here with code tags. If it is crazy big, pastebin it and then post the link.
If this is really all the information it gives about the journal being nuts, then you might want to enable debug levels of logging for the journal and then see if you can gather more information that way. This can either by done by using a drop-in snippet to the unit file, or by turning on debug levels for the entire system from the kernel command line.
The journal is not designed in such a way that it can be continously written to. There are safeguards in place to ensure that masively spamming services are cut off after a certain number of log messages in a given timeframe. Additionally, even the flush from the journal in RAM to the disk is only done periodically.

[SOLVED] Systemd journal not preserved through reboot

Similar Messages

Maybe you are looking for