[SOLVED] Systemd breaks truecrypt
Today I got my system up to date, then decided to try systemd by putting init=/bin/systemd in my grub kernel line (not in the fallback line though). Now everything looks cool booting, but when I get into lxde and run truecrypt to mount my volume, I get a fail message from truecrypt after entering my password, "Failed to set up a loop device: <my container>"
I can find the container in the correct place.
If I reboot the fallback, which doesn't use systemd, I can mount this volume no problem. Going back to systemd, I can't.
I have checked that loop is there with lsmod. I find no thread here with this problem, nor with a general google.
I haven't done anything else to further implement systemd other than installing systemd-arch-units.
The only thing that looked a bit strange in the systemd journal is "systemd-tmpfiles[289]: Two or more conflicting lines for /tmp configured, ignoring."
Last edited by PaulBx1 (2012-06-02 01:51:48)
Wrong again, it was not the upgrade. It was the fact rc.conf is not being run in systemd native mode.
FYI, to fix this I followed the procedure here:
https://wiki.archlinux.org/index.php/Sy … uring_boot
That is I created the file /etc/modules-load.d/truecrypt.conf:
# truecrypt needs to have loop loaded
loop
This had previously been loaded in /etc/rc.conf when using the sysv boot (the "MODULES" array). BTW it might be a good idea to modify the systemd wiki page saying that anything that happened in rc.conf now has to be handled in a different way, since (I guess) rc.conf is no longer being run. Er, I guess it does say that at one point, but it didn't really jump out at me. Also, the very last sentence of the truecrypt wiki page needs additional information concerning systemd. I suppose I need to figure out how to modify wiki pages...
Similar Messages
-
[SOLVED] systemd 207, lvm2 and luks booting issue
Hi
i'm using an encrypted lvm (luks) on my notebook.
/boot on /dev/sda1
lvm on /dev/sda2
main-root
main-home
main-swap
since the systemd 207 upgrade i am unable to boot my system.
this error appears at startup:
A start job is running for dev-mapper-main\x2droot.device
so i'm guessing that systemd is unable to use the encrypted lvm2, since this error is aknowledged on the
after checking some threads i tried:
mkinitcpio -p linux
but there was no effect.
HOOKS="base systemd autodetect block keymap encrypt lvm2 filesystems fsck vbox
some people tried suggesting downgrading to systemd 204 but i dont have any pkg file and building with abs leads to the following error
while makepkg -s:
==> Starting prepare()...
patching file src/core/swap.c
Hunk #1 FAILED at 220.
1 out of 1 hunk FAILED -- saving rejects to file src/core/swap.c.rej
==> ERROR: A failure occured in prepare().
Aborting...
am i supposed to remove the patches from the build? i'm not really sure and more of a beginner in this area.
Can anyone help me solve either the build or the boot issue ?
i should mention that i am only able to access my system by using chroot from an arch boot stick.
Thank you so much.
Kind Regards
Last edited by ziv667 (2013-10-01 11:27:06)https://wiki.archlinux.org/index.php/Mk … mmon_hooks
systemd: This will install a basic systemd setup in your initramfs, and is meant to replace the 'base', 'usr', 'udev' and 'timestamp' hooks. Other hooks (like encryption) would need to be ported, and may not work as intended. As of systemd 207, this hook does not work as intended when combined with lvm2 and may break your boot. You also may wish to still include the 'base' hook (before this hook) to ensure that a rescue shell exists on your initramfs.
Have you tried keeping udev instead of replacing it with systemd hook?
Have you tried https://wiki.archlinux.org/index.php/Ar … ck_Machine ? It has systemd 204.
Last edited by karol (2013-10-01 11:16:57) -
[SOLVED]systemd and make a camera visible GUI-wise in your filemanager
After reading a lot about systemd in the wiki and in this forum I understand there are different opionons about systemd. Anyway, I have a adapted all the changes to rc.conf leaving out only a few daemons to start there. So why not give systemd a try? If you dont want to read the full posting I finally got it to work, basically by reading carefully and checking the suggested tests in the systemd wiki. (loginctl)
As suggested by the wiki, I tried the systemd yesterday. Enabled via systemctl some services to "replace" my rc.conf daemons. I got what I thought everything to work, including autologin directly to my Xfce4 desktop. Everything except the digital camera.
When starting Arch traditionally via initscripts I immediately can see the camera in the filemanager (Nautilus) when the camera is attached via USB.
Some minutes later, after adding "init=/usr/lib/systemd/systemd" to the APPEND line in Syslinux and rebooting, my machine reboots
fine.But when connecting the camera again it is not visible graphically.
The camera is there because when using gphoto2 (the commandline) as root I can transfer pictures etc.
Even if I am no happy CLI user I can handle it when necessary. Handling pictures a graphical view of them is much easier...
As the wiki about systemd says one can try it out. I have not removed anything from the system and when starting Arch again, the initscript way, I can see the camera again in my filemanager, gthumb works again and pictures can be transferred to my machine.
In the wiki again, this time about digital cameras
Permission issues
Camera devices should be granted permission using ACLs. For this to work, users need to have consolekit or systemd running and the user session must be registered with them accordingly.
Check this using /usr/bin/ck-list-sessions to verify a value of "TRUE" should be returned for both the "active" and "is-local" fields:
$ ck-list-sessions | grep TRUE
active = TRUE
is-local = TRUE
ACL=Atlantic Container Line is what first comes into my mind. I have had some connections to transport business...I admit I had to google it to find the correct interpretation of this mumbo-jumbo.
The wiki also gives a "hint", if this is not working try to use the obsolete camera group and edit some udev rules.
Should not be necessary when it has worked before systemd and earlier experiences
But what is this about "Permission issues"? Here is my listings relative the wiki hints. All seems OK.. or why the heck are there two sessions??
[leif@krasaki ~]$ ck-list-sessions | grep TRUE
is-local = TRUE
active = TRUE
is-local = TRUE
[leif@krasaki ~]$ ck-list-sessions
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ''
x11-display-device = ''
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:12:56.499847Z'
login-session-id = '1'
idle-since-hint = '2012-10-24T07:13:26.994037Z'
Session2:
unix-user = '1000'
realname = '(null)'
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2012-10-24T07:13:02.361157Z'
login-session-id = '1'
[leif@krasaki ~]$
As one can see, the ACTIVE values are here as the wiki says. But no camera. Those values are the same, wheter which way the machine is started. But 2 sessions??
Further reading in the systemd wiki article and consolekit vs systemd.logind gives a clue.
From the wiki:
In order to check the status of your user session, you can use loginctl. To see if your user session is properly set up, check if the following command contains Active=yes. All polkit actions like suspending the system or mounting external drives with Udisks should then work automatically.
So when started via systemd and running logintctl, it gives this surprising result. Does not matter wheter as normal user, nor as root....
[leif@krasaki ~]$ loginctl
SESSION UID USER SEAT
1 1000 leif seat0
1 sessions listed.
[leif@krasaki ~]$ loginctl show-session 1
Id=1
Timestamp=Wed, 24 Oct 2012 10:57:03 +0200
TimestampMonotonic=20040019
DefaultControlGroup=name=systemd:/user/leif/1
VTNr=1
TTY=tty1
Remote=no
Service=login
Leader=315
Audit=1
Type=tty
Class=user
Active=no
State=online
KillProcesses=no
IdleHint=yes
IdleSinceHint=1351069009642296
IdleSinceHintMonotonic=6664433
Name=leif
[leif@krasaki ~]$
Surprising? Should it not have been Active=Yes? So something is wrong in my settings although it had worked "before" starting using systemd..
OK, so far. Lost? Not yet. Double check again everything and I found the culprit, my ~/.bash_profile which had worked before seemed a bit different to what is suggested in the wiki. The old one, actually started 2 sessions, as also could be seen here above checking ck-list-sessions. That was the problem
Using a fresh edited ~/.bash_profile as suggested here, the camera is visible graphically
Finally, just for fun, start again the old initscipt way. Enabling daemon and so on. Still 2 sessions going on....Here it was the "/.xinitrc, which also had some old fashions and I removed the ck-launch-session from the exec line. So even here, now only 1 session..
Anyway, now the camera is visible, both starting with initscripts, naturally also some daemons active in rc.conf and by starting with systemd.
I rest my case and it seems systemd works with everything on my machine which is just a normal desktop used by an old man.
Thanks for reading...Solved now! Boot times are as fast as posssible on my HDD I think. Only thing after uninstalling initscripst and initscripts-systemd was that locale was not set inspite of a correct /etc/locale.conf. I had to make /etc/profile.d/locale.sh with this content;
if [ -s /etc/locale.conf ]; then
. /etc/locale.conf
fi
export LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE
export LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
export LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION -
[solved] systemd power control doesn't work
Since there is no way of getting systemctl power control work without sudo, I tried modifying sudoers to allow my user to operate them without password.
However, it still won't work.
I tried that
cross ALL = NOPASSWD: /usr/sbin/hibernate,/usr/bin/systemctl suspend,/usr/bin/systemctl reboot,/usr/bin/systemctl suspend,/usr/bin/systemctl hibernate
and I tried that
cross ALL = NOPASSWD: /usr/bin/systemctl
The result was the same:
$ systemctl suspend
Failed to issue method call: Access denied
Failed to issue method call: Access denied
Last edited by impact (2012-11-09 11:28:17)impact wrote:
Since there is no way of getting systemctl power control work without sudo, I tried modifying sudoers to allow my user to operate them without password.
However, it still won't work.
I tried that
cross ALL = NOPASSWD: /usr/sbin/hibernate,/usr/bin/systemctl suspend,/usr/bin/systemctl reboot,/usr/bin/systemctl suspend,/usr/bin/systemctl hibernate
and I tried that
cross ALL = NOPASSWD: /usr/bin/systemctl
The result was the same:
$ systemctl suspend
Failed to issue method call: Access denied
Failed to issue method call: Access denied
you have to use "sudo systemctl suspend" still, sudoers is only affecting sudo behavior as it was mentioned...
nahuy_systemd wrote:systemd very bad system. I solved this. I moved to CRUX.
...and you registered to the forum just to tell us that? well, if I were you, i would either change the doctor or make him prescribe me another pills -
[SOLVED]systemd-tmpfiles-setup.service failure
Hi guys,
I just reinstalled arch with the following partitions:
[root@arch_vinnom vinnom]# gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.0
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): BD3CA679-FA08-4F60-9BAD-B845DE9FF7EB
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625142414
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 BIOS
2 4096 52432895 25.0 GiB 8300 ROOT
3 52432896 53481471 512.0 MiB 8300 BOOT
4 53481472 74452991 10.0 GiB 8300 TMP
5 74452992 95424511 10.0 GiB 8300 VAR
6 95424512 602935295 242.0 GiB 8300 HOME
7 602935296 625142414 10.6 GiB 8200 SWAP
The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
# 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.
[Unit]
Description=Temporary Directory
Documentation=man:hier(7)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/tmp
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
[Mount]
What=tmpfs
Where=/tmp
Type=tmpfs
Options=mode=1777,strictatime
Because of this, I'm always getting:
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Dom 2015-05-03 03:29:58 BRT; 27min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 278 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 278 (code=exited, status=1/FAILURE)
Then I tried to change '/tmp' to '/run/tmpfs', folder that I created for this, using tmpfs wiki as reference.
# 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.
[Unit]
Description=Temporary Directory
Documentation=man:hier(7)
Documentation=http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
ConditionPathIsSymbolicLink=!/run/tmpfs
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
[Mount]
What=tmpfs
Where=/run/tmpfs
Type=tmpfs
Options=mode=1777,strictatime,nodev,nosuid,size=1536M
But the error persists. What I'm missing?
Last edited by vinnom (2015-05-03 16:51:38)ooo wrote:Couldn't you just mask the tmp.mount service? (as mentioned in the wiki page you linked)
Then your /tmp partition would be mounted according to your fstab
Raynman wrote:
The tmp.mount generated from your fstab should override the tmp.mount in /usr/lib/systemd/system. You say
The problem is that tmpfs is mounted at '/tmp' through '/usr/lib/systemd/system/tmp.mount'
If that is true (could you show output of mount and your fstab?) that is worth investigating.
However, your original problem seems to be that systemd-tmpfiles-setup.service fails. If something is wrong with your mounts, that could be related, but it might very well be something else. Is there any more information in the journal to indicate why the service fails (maybe even mentioning a tmpfiles.d config file that is responsible)? Did you create any config files for tmpfiles.d yourself?
Sorry guys, I tried to be concise, but ended up that I didn't make myself clear.
My '/tmp' is mounting fine as it takes priority over systemd. In fact, what I wanted to say is that '/tmp' mounts fine, systemd tried to mount tmpfs at '/tmp' and fails and I want to point tmpfs to mount at '/run/tmpfs' which I created for this, but just editing '/usr/lib/systemd/system/tmp.mount' didn't solve.
As for journalctl, it repeats several times this message:
Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Mai 02 22:43:32 arch_vinnom systemd[1]: Failed to start Create Volatile Files and Directories.
Mai 02 22:43:32 arch_vinnom systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Mai 02 22:43:32 arch_vinnom systemd[1]: systemd-tmpfiles-setup.service failed.
foutrelis wrote:
Depending on how your '/var' file system is created/mounted, you might need to enable ACL on it:
https://wiki.archlinux.org/index.php/Sy … rt_at_boot
hmm
I created my /var during arch installation, with mkfs.reiserfs.
Using
tune2fs -l /dev/sdXY | grep "Default mount options:"
To check if acl was already enabled, I got:
[root@arch_vinnom vinnom]# tune2fs -l /dev/sda5 | grep "Default mount options:"
tune2fs: Bad magic number in super-block while trying to open /dev/sda5
Couldn't find valid filesystem superblock.
Then I searched a bit and noted that reiserfs isn't compatible with acl =/
Last edited by vinnom (2015-05-03 15:12:18) -
Read only after install [SOLVED -- systemd related]
Anyone know why a new (booted ~2-3 times) install would suddenly mount read-only? /etc/fstab is fine, /etc/mtab reports rootfs / as rw, and I am logged in as root, but I get "read-only filesystem", hence there are no logs, etc.
Last edited by goldilocks (2012-10-14 18:01:41)DSpider wrote:You probably removed "ro" from syslinux.cfg.
Nope. I have a startup service I use on fedora, and since the target I usually use wasn't apparent, I casually systemctl enabled it with WantedBy=local-fs.target, figuring if that was too early it would just fail (it writes to to disk).
Using "mount -o remount,rw /" worked, so I tried a few things like switching fstab to use a UUID instead of a device node, that didn't work. Finally I disabled the service and everything is back to normal.
I did this a couple of times (enabling, rebooting, disabling, rebooting) just to confirm that was the cause. I guess that target runs before the rw remount, maybe this causes systemd to crap out in some way. Shame it can't just fail the service, log it, and continue. Maybe even an oversight verging on "bug", though I am sure they are aware of it already.
I'd mark this "SOLVED" but I don't see a button...
Last edited by goldilocks (2012-10-14 17:49:16) -
[Solved] systemd-user-session: Best way to pass global ENV vars?
Hey guys,
So when using the [email protected] from the user-session-units what's the best / cleanest way to set global environment variables for that systemd --user instance (and thus, all programs spawned from it)?
What I'm talking about is /etc/profile and $HOME/.profile.
For example, I usally configure my XDG_CONFIG_HOME and XDG_CACHE_HOME in my ~/.profile. But since systemd --user is being started by systemd --session none of these environment variables are loaded.
The solution I've come up is to change the ExecStart in the [email protected] file to something like this:
ExecStart=/usr/bin/sh -c "source /etc/profile; source $HOME/.config/bash/environment; exec /usr/lib/systemd/systemd --user"
I know I could use the `EnvironmentFile` option to load the environment variables from a file, but it's not as flexable as a bash script.
Am I thinking about this problem wrong? Is there a more "systemd --user"-y way of solving the problem?
Last edited by EvanPurkhiser (2013-08-12 03:02:48)I've more or less solved this using my own user-session units. I still don't know if my method would really be considered the proper way or not though.
Last edited by EvanPurkhiser (2013-08-12 03:02:19) -
[SOLVED] systemd --user: "Failed to open private bus connection:"
EDIT: The solution was to set DBUS_SESSION_BUS_ADDRESS, as suggested by gtmanfred in irc. By putting the following before executing systemd --user, the error vanished:
export DBUS_SESSION_BUS_ADDRESS=/run/user/$(id -u)/dbus/user_bus_socket
===================
Original problem:
Everything on my box appears to be working ok, but I'm getting this error consistently in tty1 and at the top of journalctl (as user) whenever I start systemd --user:
systemd[3975]: Failed to open private bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
I roughly have my system setup per this wiki section https://wiki.archlinux.org/index.php/Sy … ur_Session. I start systemd --user via a small script in my .bash_profile. Here are my relevant dbus{.service,socket} files, from the package user-session-units mentioned in the wiki: (Edit: xorg is started through xorg-launch-helper, also from that wiki page) Edit2: I'm not using autologin. I noticed that under the autologin section of that page, DBUS_SESSION_BUS_ADDRESS is set to some path. In my setup that isn't set anywhere, so I may try to copy that later but I don't have time to play with it right now. Will post back later.
=====/usr/lib/systemd/user/dbus.service=====
[Unit]
Description=D-Bus System Message Bus
Requires=dbus.socket
[Service]
ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork --systemd-activation
ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
=====/usr/lib/systemd/user/dbus.socket=====
[Unit]
Description=D-Bus System Message Bus Socket
[Socket]
ListenStream=%t/dbus/user_bus_socket
And the output of sudo systemctl status dbus:
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Tue 2013-02-05 14:50:30 EST; 22min ago
Main PID: 369 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─369 /usr/bin/dbus-daemon --system --address=systemd: --no...
Feb 05 14:50:30 sellers-laptop systemd[1]: Starting D-Bus System Message Bus...
Feb 05 14:50:30 sellers-laptop systemd[1]: Started D-Bus System Message Bus.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
I'm not sure what the error even means or how to go about debugging it. Any suggestions would be appreciated.
Last edited by Feynman (2013-02-05 22:07:23)NVM...didn't notice it was already solved.
Last edited by the sad clown (2013-02-05 22:33:10) -
[SOLVED] systemd adsl service does not start
After the today's upgrade of my system I get lines like this in my journal, as the adsl service does not want to start.
# router systemd[522]: Failed at step EXEC spawning /usr/sbin/pppoe-start: No such file or directory
The problem is, that pppoe-start is in /usr/bin/ and not in /usr/sbin. According to pacman (pacman-Ql rp-pppoe) /usr/bin/ is the correct location.
I really don't know, why systemd is trying to launch it, because even the service file (/usr/lib/systemd/system/adsl.service) points to the correct location.
[Unit]
Description=ADSL Deamon
[Service]
Type=forking
ExecStart=/usr/bin/pppoe-start
ExecStop=/usr/bin/pppoe-stop
[Install]
WantedBy=multi-user.target
The service is launching and stopping with pppoe-start and pppoe-stop.
When launched, it also shuts down fine when stopping it by
systemctl stop adsl
Why the hell is it trying to launch from /usr/sbin/?
Last edited by scar (2013-06-04 13:07:23)It goes definitely against any logic.
The service file looks good, but I've copied it to /usr/lib/systemd/system/bdsl.service. Same contents - and the new one launches succesfully.
I've deleted the original ...adsl.service file, verified that it disappeared, copied it back from the new bdsl.service file, and it still does not launch.
[EDIT]
I've erased the drive, restored the system from a 1 week old backup, started it - everything worked. Then I'v updated the whole system, including the rp-pppoe package, and the adsl service is failing again.
Downgrading solves the problem. Should I file a bug report?
Last edited by scar (2013-06-01 10:14:41) -
[SOLVED] systemd+wpa_supplicant, but the name of interfaces changes
Hello,
I'm following instructions here for having the wireless connection ready at boot on my machine.
I needed to setup two different daemons since sometimes my wireless interfaces is wlp3s0 and sometimes is wlan0.
When the name of the interface is wlp3s0 everything works fine and I'm correctly given an IP address.
It doesn't happen the same when the name is wlan0.
Here's some output
$ systemctl status [email protected] -l
● [email protected] - Wireless network connectivity (wlan0)
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: inactive (dead)
Jun 22 16:10:19 banzi systemd[1]: Dependency failed for Wireless network connectivity (wlan0).
$ cat /etc/conf.d/network-wireless@wlan0
address=192.168.1.10
netmask=24
broadcast=192.168.1.255
gateway=192.168.1.1
$ cat /etc/conf.d/network-wireless@wlp3s0
address=192.168.1.8
netmask=24
broadcast=192.168.1.255
gateway=192.168.1.1
$ cat /etc/systemd/system/[email protected]
[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/conf.d/network-wireless@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/wpa_supplicant -B -i %i -c /etc/wpa_supplicant/wpa_supplicant.conf
ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
ExecStart=/usr/bin/ip route add default via ${gateway}
ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=multi-user.target
What more info do you need?, what's wrong?
Thanks,
Giuseppe
Last edited by giuscri (2014-06-28 19:53:35)Check your journal for messages relating to wlan0 and wlp3s0. I think you may find some kind of error message -- maybe having to do with firmware. I've seen thing like that break predicatible device names
If you've just one wlan interface, you could turn off predicable device names and just go with wlan0 -
[SOLVED] Systemd stuck at "Starting File system check"
Hi all
Backstory
My hardware:
Mobo: Gigabyte X99 2011v3 with UEFI and dual bios.
GFX: MSI GTX 970 4GB Gaming OC
HDD: Samsung 850 Pro 1TB SSD
CPU: intel 5820k
I have been using arch for about 2 years now. I recently bought new hardware, Gigabyte X99 motherboard uefi dual bios. I have tried a couple of times to install arch the old way, i.e. legacy mode or normal bios mode, however after a successful install, when I reboot my bios says "Select Proper Boot Device". Then I decided to put everything in UEFI mode and install arch using the uefi install disc. At first, I was not very successful, because I followed the arch wiki to the bone but when it comes to UEFI, instructions are a bit vague. In any case, I managed to install Arch and get uefi to work 100% by using this guide http://jorisvandijk.com/2014/installing … pt-system/ .
Problem
After installing arch successfully using UEFI mode, arch starts booting up, everything shows [OK] at the side, no errors, however, it hangs after a line that reads "Starting File system check ". I am not at home right now, however I thought I could start troubleshooting and maybe get some ideas.
I have tried the following.
- Chrooted back into my arch install using the live cd and mounting my partitions.
- Updated and synced pacman.
- Removed all journal log files.
- reinstalled Systemd.
- rebuilt kernel modules.
none of the above worked. It still hangs at "Starting fiel system check"
Any ideas.
SOLUTION
Solved by using
nolapic
Still had other problems after that, however, the initial problem was solved.
Last edited by janpansa (2015-02-26 20:04:24)jasonwryan wrote:Taking the time to read through the relevant pages and working through the Beginners' Guide methodically is the best (and only) way to both install Arch and also bed in a sound understanding of how your system is put together. It is an investment that will continue to pay you back as long as you run a Linux/UNIX box.
Hi Jason,
thx for your help so far. I have printed out the Arch beginners install and followed it to the bone and focusing on the UEFI parts. Arch installed without a single error, everything went smooth. Aftwerwards, I exited from the chroot environmount, unmount and reboot and again, it hangs on the startup. This time I took screenshots.
I present to the board, exhibit A, arch starting up after a fresh install :
http://oi61.tinypic.com/2m4x82o.jpg
I now present to the board, exhibit B, arch starting up for a second time, after restarting the pc :
http://oi59.tinypic.com/10ehvki.jpg
Afterwards, I restarted again. Went into bios setup and checked my boot priorities. This is what I saw:
I now present exhibit C, my bios boot options :
http://oi62.tinypic.com/24ys0bd.jpg
I tried all the options listed for my Samsung SSD, with and without UEFI as well as the option that was the default aka Linux boot manage". Each one did exactly the same.
I have a few ideas :
1.) Leave out swap.
2.) Disable fscheck.
3.) I have a feeling that my SSD is reading/writing too fast and that fscheck is having trouble ?
I am now trying option 1. In other words, I am reinstalling arch, again, following the beginners guide to the bone and focusing specifically on the UEFI parts. This time, I am leaving out swap. (I have 16GB of DDR4 memory). I have about a 70% feeling that the outcome will be the same. However, I will be back after that to comment on the outcome. Please leave feedback and help me through this where you can ! Thanks
Last edited by jasonwryan (2015-02-23 19:34:21) -
[SOLVED] systemd-modules-load fails
.. because it cannot find gspca. My log:
journalctl -xn
-- Logs begin at Thu 2013-08-22 11:43:18 CEST, end at Mon 2014-06-23 14:26:30 CEST. --
Jun 23 14:25:21 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop7" has new interfaces: ("org.
Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop2" has new interfaces: ("org.
Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop1" has new interfaces: ("org.
Jun 23 14:25:22 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" has new interfaces: ("org.
Jun 23 14:26:19 jiggs org.kde.knotify[1825]: "/org/freedesktop/UDisks2/block_devices/loop0" lost interfaces: ("org.fre
Jun 23 14:26:30 jiggs systemd[1]: Starting Load Kernel Modules...
-- Subject: Unit systemd-modules-load.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-modules-load.service has begun starting up.
Jun 23 14:26:30 jiggs systemd-modules-load[3138]: Failed to find module 'gspca'
Jun 23 14:26:30 jiggs systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Jun 23 14:26:30 jiggs systemd[1]: Failed to start Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-modules-load.service has failed.
-- The result is failed.
Jun 23 14:26:30 jiggs systemd[1]: Unit systemd-modules-load.service entered failed state.
But I have lots of gspca's:
# ls /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca
gl860 gspca_kinect.ko gspca_ov534.ko gspca_sonixj.ko gspca_sq905c.ko gspca_topro.ko
gspca_benq.ko gspca_konica.ko gspca_pac207.ko gspca_spca1528.ko gspca_sq905.ko gspca_tv8532.ko
gspca_conex.ko gspca_main.ko gspca_pac7302.ko gspca_spca500.ko gspca_sq930x.ko gspca_vc032x.ko
gspca_cpia1.ko gspca_mars.ko gspca_pac7311.ko gspca_spca501.ko gspca_stk014.ko gspca_vicam.ko
gspca_etoms.ko gspca_mr97310a.ko gspca_se401.ko gspca_spca505.ko gspca_stk1135.ko gspca_xirlink_cit.ko
gspca_finepix.ko gspca_nw80x.ko gspca_sn9c2028.ko gspca_spca506.ko gspca_stv0680.ko gspca_zc3xx.ko
gspca_jeilinj.ko gspca_ov519.ko gspca_sn9c20x.ko gspca_spca508.ko gspca_sunplus.ko m5602
gspca_jl2005bcd.ko gspca_ov534_9.ko gspca_sonixb.ko gspca_spca561.ko gspca_t613.ko stv06xx
The only difference I have with respect to a standard installation is that I downloaded an older version of the backport drivers, and in doing so I surely re-installed gspca.
So my questions are: where is systemd-module-load searching for gspca? How can I persuade it to search in the right directory? And in any case, why is it searching for it in the wrong place to start with?. Just in case,
# uname -a
Linux jiggs 3.15.1-1-ARCH #1 SMP PREEMPT Tue Jun 17 09:32:20 CEST 2014 x86_64 GNU/Linux
Last edited by MariusMatutiae (2014-06-26 09:10:22)Problem solved, thanks to both of you guys. For some resason, I had a webcam.conf file in /etc/modules-load.d containing the single line *gspca*, which is not a module: both modprobe and insmod fail, because the correct module name is one of those listed in /lib/modules/`uname -r`/kernel/drivers/media/usb/gspca. They are called gspca_benq.ko gspca_konica.ko and so on. I simply deleted the file since I do not need it.
As for backport drivers: this site, http://drvbp1.linux-foundation.org/~mcg … backports/ has the most recent versions of Linux drivers, backported so that older kernels can install them (I understand this is not a concern for fellow Archers). Whenever I need to upgrade (mostly on Debian) or downgrade (a few times on Arch, because an older version of a driver is free of a newly minted bug) I download these drivers, compile them and install them from source. -
[SOLVED]Systemd autostart conky
Hi guys, as a new Arch user I tried to play a bit with systemd to have it automatically start Conky after logon. When I try to start conky manually from the terminal it all works perfectly but when systemd needs to do it as a unit (service) it's not possible as Conky doesn't accept the rc file it's been given. It seems that the variable $HOME or %h is unknown to systemd. Below some details
Starting my 2 Conky files from the Gnome terminal is no problem:
conky -d -c $HOME/.Conky/ConkyToprc
conky -d -c $HOME/.Conky/ConkyLogrc
cat /etc/systemd/system/conky.service:
[Unit]
Description=Conky system monitor
Documentation=man:conky(1)
[Service]
Type=forking
ExecStart=/usr/bin/conky -d -c /home/viper/.Conky/ConkyToprc
[Install]
WantedBy=xinitrc.target
[root@Arch viper]# systemctl status conky.service
● conky.service - Conky system monitor
Loaded: loaded (/etc/systemd/system/conky.service; disabled)
Active: failed (Result: core-dump) since Fri 2014-05-16 18:39:51 CEST; 10min ago
Docs: man:conky(1)
Process: 4833 ExecStart=/usr/bin/conky -d -c /home/viper/.Conky/ConkyToprc (code=dumped, signal=ABRT)
May 16 18:39:51 Arch conky[4833]: Conky: $HOME environment variable doesn't exist
May 16 18:39:51 Arch conky[4833]: conky: malloc.c:2369: sysmalloc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == ...
May 16 18:39:51 Arch systemd-coredump[4834]: Process 4833 (conky) dumped core.
May 16 18:39:51 Arch systemd[1]: conky.service: control process exited, code=dumped status=6
May 16 18:39:51 Arch systemd[1]: Failed to start Conky system monitor.
May 16 18:39:51 Arch systemd[1]: Unit conky.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
So even after changing the systemd unit file to use the full path /home/viper/.Conky/ConkyToprc it's still not working. I think after changing $HOME or %h Conky did accept the config file but doesn't recognize the $HOME variable in the config file anymore. Or maybe I'm missing something here... And I'm not even trying to load the second conky file Anyone an idea as where I need to look? Any help is highly appreciated. Thank you in advance.
It seems to be a bit related to this: http://lists.freedesktop.org/archives/s … 06217.html
Last edited by DarkLite1 (2014-05-17 16:48:04)Thank you everyone for your feedback, I really appreciate it Some things I would still like to clarify although I fully agree with your reasoning of not using systemd for my 'conky' idea here.
@ANOKNUSA: Yes you are right, systemd starts everything simultaneously at boot time. The way I did my test was to start the unit manually from the Gnome terminal after already being logged on to Gnome. So in my point of view the $HOME variable did already exist at that point and there was no need to wait for the X server... So in theory, it should've been able to get the job done.
@twelveeighty: So yes, I do believe you are right. systemd doesn't know $HOME at all.
Than my final question to have this solved for me. What is the best way to have 2 instances of Conky running with each it's own config file? I tried the following already, but it was unsuccessful:
cat /etc/profile.d/autostart.sh
Exec=/usr/sbin/conky -d -c /home/viper/.Conky/ConkyToprc
Exec=/usr/sbin/conky -d -c /home/viper/.Conky/ConkyLogrc
cat /usr/share/gnome/autostart/conky.desktop
[Desktop Entry]
Type=Application
Name=Conky
Comment=Start conky script
Exec=/usr/sbin/conky -d -c /home/viper/.Conky/ConkyToprc
Exec=/usr/sbin/conky -d -c /home/viper/.Conky/ConkyLogrc
OnlyShowIn=GNOME;
X-GNOME-Autostart-Phase=Application
When trying to follow the proposed solution found here https://wiki.archlinux.org/index.php/xinitrc there is no example file availble for .xinitrc in /etc/skel as suggested 'Copy the sample /etc/skel/.xinitrc file to your home directory' And if there was, how would the syntax be for 2 instances of Conky? Because when I read the Note it's not possible to add 2 lines of EXEC:
Note: Make sure to uncomment only one exec line, since that will be the last command run from the script; all the following lines will just be ignored. Do NOT attempt to background your WM by appending a `&` to the line.
/again: thanks for still helping me out and reading my jibber/jabber. I sometimes really feel like a noob here between all you pro's. But the only way of getting there is by falling and learning how to get up? Right Bruce?
Last edited by DarkLite1 (2014-05-17 16:18:43) -
(Solved) systemd-journald extremely high CPU usage
I started noticing this problem a few days ago, but I thought it was because I was running too much with too little RAM. But when running nothing more than a KDE desktop, my CPU usage bounces between 50% and 100%, making things laggy. It looks like systemd-journald is to blame, as it is using 50% of the CPU. This is an AMD Phenom II dual core, so this definitely shouldn't be happening. I noticed journal logs were more than 2 GB, so I deleted everything within /var/log/journal/. Rebooted, no change, so I disabled journal storage, but that did not solve the problem.
Nothing in the logs looks like a problem to me:
$ sudo journalctl
-- Logs begin at Tue 2013-03-12 17:31:37 PDT, end at Tue 2013-03-12 18:15:56 PDT. --
Mar 12 17:31:37 silverstone systemd-journal[149]: Allowing runtime journal files to grow to 298.6M.
Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpuset
Mar 12 17:31:37 silverstone kernel: Initializing cgroup subsys cpu
Mar 12 17:31:37 silverstone kernel: Linux version 3.7.10-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.2 (G
Mar 12 17:31:37 silverstone kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=31669ea0-76db
Mar 12 17:31:37 silverstone kernel: e820: BIOS-provided physical RAM map:
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000000e2000-0x00000000000fffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cff8ffff] usable
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff90000-0x00000000cff9dfff] ACPI data
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cff9e000-0x00000000cffdffff] ACPI NVS
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000cffe0000-0x00000000cfffffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
Mar 12 17:31:37 silverstone kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001afffffff] usable
Mar 12 17:31:37 silverstone kernel: NX (Execute Disable) protection: active
Mar 12 17:31:37 silverstone kernel: SMBIOS 2.5 present.
Mar 12 17:31:37 silverstone kernel: DMI: MSI MS-7642/890GXM-G65 (MS-7642) , BIOS V1.2 03/31/2010
Mar 12 17:31:37 silverstone kernel: e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
Mar 12 17:31:37 silverstone kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Mar 12 17:31:37 silverstone kernel: No AGP bridge found
Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0x1b0000 max_arch_pfn = 0x400000000
Mar 12 17:31:37 silverstone kernel: MTRR default type: uncachable
Mar 12 17:31:37 silverstone kernel: MTRR fixed ranges enabled:
Mar 12 17:31:37 silverstone kernel: 00000-9FFFF write-back
Mar 12 17:31:37 silverstone kernel: A0000-EFFFF uncachable
Mar 12 17:31:37 silverstone kernel: F0000-FFFFF write-protect
Mar 12 17:31:37 silverstone kernel: MTRR variable ranges enabled:
Mar 12 17:31:37 silverstone kernel: 0 base 000000000000 mask FFFF80000000 write-back
Mar 12 17:31:37 silverstone kernel: 1 base 000080000000 mask FFFFC0000000 write-back
Mar 12 17:31:37 silverstone kernel: 2 base 0000C0000000 mask FFFFF0000000 write-back
Mar 12 17:31:37 silverstone kernel: 3 disabled
Mar 12 17:31:37 silverstone kernel: 4 disabled
Mar 12 17:31:37 silverstone kernel: 5 disabled
Mar 12 17:31:37 silverstone kernel: 6 disabled
Mar 12 17:31:37 silverstone kernel: 7 disabled
Mar 12 17:31:37 silverstone kernel: TOM2: 00000001b0000000 aka 6912M
Mar 12 17:31:37 silverstone kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Mar 12 17:31:37 silverstone kernel: e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
Mar 12 17:31:37 silverstone kernel: e820: last_pfn = 0xcff90 max_arch_pfn = 0x400000000
Mar 12 17:31:37 silverstone kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff880
Mar 12 17:31:37 silverstone kernel: initial memory mapped: [mem 0x00000000-0x1fffffff]
Mar 12 17:31:37 silverstone kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
$ systemctl status systemd-journald
systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Tue 2013-03-12 18:10:41 PDT; 8min ago
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 142 (systemd-journal)
Status: "Processing requests..."
CGroup: name=systemd:/system/systemd-journald.service
`-142 /usr/lib/systemd/systemd-journald
However, it looks like the log files keep getting corrupted:
$ sudo journalctl --verify
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000007f543-0004d7c4445effa4.journal
Invalid object contents at 124687944ââââââââââââââââââââââââââââââââââââââââââ 49%
File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal:124687944 (of 134074368, 92%).
FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000a8cb7-0004d7c3d52e9748.journal (Bad message)
Invalid object contents at 75715936âââââââââââââââââââââââââââââââââââââââââââ 49%
File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal:75715936 (of 76156928, 99%).
FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system.journal (Bad message)
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000290d6-0004d7c3a0033472.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000000001-0004d7c413227650.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000fcfc0-0004d7c3fd8ee9c5.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/[email protected]~
Invalid object contents at 124701856ââââââââââââââââââââââââââââââââââââââââââ 49%
File corruption detected at /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal:124701856 (of 134049792, 93%).
FAIL: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-0000000000000001-0004d7c3876dda65.journal (Bad message)
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-00000000000a9da8-0004d7c45187e39e.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000d26b1-0004d7c3ea1b73f7.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-000000000002a43f-0004d7c425785944.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-00000000000539fb-0004d7c3b2d1f935.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@5e6edd359123491f9998a310206ccbf9-0000000000054d23-0004d7c4354da4ef.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@2c1af599e637441985385fe37ded2a2c-0000000000001706-0004d7c38cd3de88.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/user-1000@5e6edd359123491f9998a310206ccbf9-00000000000019b4-0004d7c4153f8628.journal
PASS: /var/log/journal/9ddaa50d8841758bb1bea9b700000f33/system@2c1af599e637441985385fe37ded2a2c-000000000007e345-0004d7c3c3ed8197.journal
I am using a two or three year old SSD, so maybe it has gotten some bad sectors? But that doesn't explain why journald still bricks things when it isn't logging anything. The install is 10 months old, and I switched from init to systemd around October. Is there anything I can do, short of reinstalling?
Thanks,
Nicholas
Last edited by bicyclingrevolution (2013-03-14 05:57:13)Thanks for the tip ilkyest, but it didn't make any difference to the systemd-journald problem.
However, I looked at journalctl again and found it cluttered with CUPS failures:
-- Logs begin at Tue 2013-03-12 19:17:00 PDT, end at Wed 2013-03-13 22:31:31 PDT. --
Mar 12 19:17:00 silverstone spideroak_inotify[796]: Program started
Mar 12 19:21:30 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 7199 messages from /system
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5471 messages from /system
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:30 silverstone systemd-journal[143]: Suppressed 5699 messages from /system
Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:27 silverstone systemd[1]: Failed to start CUPS Printing Service.
Mar 12 19:21:27 silverstone systemd[1]: Starting CUPS Printing Service...
Mar 12 19:21:27 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:30 silverstone systemd-coredump[1592]: Process 1590 (cupsd) dumped core.
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-Gray..
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_3840-RGB..
Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_3840
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-Gray..
Mar 12 19:21:28 silverstone colord[354]: Profile added: Deskjet_F4100-RGB..
Mar 12 19:21:28 silverstone colord[354]: Device added: cups-Deskjet_F4100
Mar 12 19:21:28 silverstone dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Mar 12 19:21:28 silverstone dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs
Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-Gray..
Mar 12 19:21:28 silverstone colord[354]: Profile removed: Deskjet_3840-RGB..
Mar 12 19:21:28 silverstone colord[354]: device removed: cups-Deskjet_3840
Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-Gray..
Mar 12 19:21:31 silverstone colord[354]: Profile removed: Deskjet_F4100-RGB..
Mar 12 19:21:31 silverstone colord[354]: device removed: cups-Deskjet_F4100
Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Mar 12 19:21:31 silverstone dbus-daemon[337]: dbus[337]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or director
Mar 12 19:21:31 silverstone systemd-journal[143]: Missed 6365 kernel messages
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone cupsd[1590]: Unknown directive DefaultAuthType on line 9.
Mar 12 19:21:31 silverstone cupsd[1590]: cupsd: client.c:757: avahi_client_get_host_name: Assertion `client' failed.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone cupsd[1594]: Unknown directive DefaultAuthType on line 9.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Mar 12 19:21:31 silverstone systemd[1]: cups.service start request repeated too quickly, refusing to start.
Disabling cups solved the CPU usage issue.
It looks like the root of the problem is Avahi failing to start, but I have no idea why it isn't working.
$ systemctl status dbus-org.freedesktop.Avahi.service
dbus-org.freedesktop.Avahi.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead) -
[SOLVED] Systemd and tmpfiles? Conflicting /tmp?
I've got this error in journal;
systemd-tmpfile[247]: Two or more conflicting lines for /tmp configured, ignoring.
This is from a leftover from arch initscripts, /usr/lib/tmpfiles.d/arch.conf shich is doubled by systemd's, /usr/lib/tmpfiles.d/x11.conf (almost).
arch.conf;
D /tmp 1777 root root 10d
d /run/daemons 0755 root root -
d /tmp/.X11-unix 1777 root root 10d
d /tmp/.ICE-unix 1777 root root 10d
d /tmp/.XIM-unix 1777 root root 10d
d /tmp/.font-unix 1777 root root 10d
d /tmp/.Test-unix 1777 root root 10d
F /run/utmp 0664 root utmp -
r /tmp/.X[0-9]-lock
r /etc/nologin
r /etc/shutdownpid
r /forcefsck
r /fastboot
x11.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 General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
# See tmpfiles.d(5) for details
# Make sure these are created by default so that nobody else can
d /tmp/.X11-unix 1777 root root 10d
d /tmp/.ICE-unix 1777 root root 10d
d /tmp/.XIM-unix 1777 root root 10d
d /tmp/.font-unix 1777 root root 10d
d /tmp/.Test-unix 1777 root root 10d
# Unlink the X11 lock files
r /tmp/.X[0-9]*-lock
Can I delete the arch one - where is it started from at boot? I'm running only systemd and got rid of all arch units. Or can I merge them? I really can't tell which tmpfiles are needed.
Last edited by swanson (2012-05-31 19:11:46)Solved now! Boot times are as fast as posssible on my HDD I think. Only thing after uninstalling initscripst and initscripts-systemd was that locale was not set inspite of a correct /etc/locale.conf. I had to make /etc/profile.d/locale.sh with this content;
if [ -s /etc/locale.conf ]; then
. /etc/locale.conf
fi
export LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE
export LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
export LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION
Maybe you are looking for
-
How can I delete an E-Mail account in Nokia 6300
I have setup an E-Mail account (e.g Gmail) on my Nokia 6300. I would like to delete this account which is no longer needed. I couldn't find any delete option there. Before Nokia 6300, I have used Nokia E-50. It has a very simple option in Connect fol
-
How create a variable in the TVARVC that calculate the last week
Hi Gurus, i need create a Variable in the table TVARVC that calculate which was the last week to run a Program in BW, i have no idea how can i do it, where do i must start? please can you tell me step by step, i will really appreciate it
-
I want to create an ID for my company for client review
I have a personal account, ID but I want to set up an ID for my company to share edits for the client review option in cs live
-
Firefox 3.66 and Flash 10.1.53.64 Crash Constantly
Ever since the install it crashes constantly.. sometimes it could go for awhile with no problems, other times like tonight it'll crash like 6 times in 2 minutes. Doesn't seem to be a certain website either. Could be YouTube, could be MySpace, could b
-
ORA-01403: no data found - refresh after insert on view
Hi all, I have problems with refresh after insert on view and i override this method on my xxDefImpl.java public boolean isUseReturningClause() { return false; Anyway what it does is to substitute the RETURNIN INTO to SELECT ID INTO ? FROM MY_VIEW WH