Several systemd services failed on fresh installation

Hi, I installed Arch with the latest iso a few weeks ago.
Now I saw services failing.
I disabled everything that refers to krb (kerberos), because I don't need it yet.
But there are 2 failed services left, I don't know how to solve them loading. Or If it is a good idea to disable them too, because I don't know what they are for:
mdadm.service
systemd-journal-upload.service
Thank you for your help.
JD

mdadm is for RAID. And for all systemd services, you can read the relevant man page to see what it does.
Not a Sysadmin issue, moving to NC....

Similar Messages

  • ITunes 9.0 install problem: iPod service fails to start, installer quits

    Hi,
    I tried to upgrade my iTunes from 8.XXX(I think it was latest 8) to 9.0 but run into this problem where the installer tries to start the iPod service and fails. The installer can not continue any more and it has to be rolled back. I uinstalled 8.xx and tried again but same result. I also tried the suggestion in another thread about stopping the AppleMobileDevice service and removing the folder but it did not help. This is the error message:
    "Product: iTunes -- Error 1920. Service 'iPod Service' (iPod Service) failed to start. Verify that you have sufficient privileges to start system services."
    I am logged in as the admin so I do have sufficient privileges.
    Is any one having the same problem? How do I make it work? I am using Win XP-Pro SP3 32bit.
    Thanks
    null

    katkeys12 wrote:
    I also unistalled the itunesbabd quicktime and now I can't get it to download. It keeps sticking. I am concerned that my library is gone. I have no way of backing my files, laptop.
    I was finally able to make it work. I did the following steps:
    1. Delete/unistall every thing related to Apple/iTunes
    2. Delete itunes folder if its still there.
    3. open MSCONFIG->General->check off 'Load Startup Items'->click 'ok'
    4. Reboot
    5. Install iTunes
    6. You can turn on Load Startup Items after iTunes installs.
    Hope this help. Thanks for all the help. It sure was annoying!!!!

  • [SOLVED] systemd : services failing to start on boot

    I have removed sysvinit completely as per the systemd wiki pages.
    I don't usually re-boot very often so I'm not sure exactly when the problem started.
    I only noticed this problem about 4 or 5 days ago.
    But now whenever I reboot my machine 2 services fail consistently.
    adsl.service
    colord.service
    They both start flawlessly once I can log in at a console.
    I'm using kde and in the last couple of days, while trying to fix my problem, the kdm service has failed to start a couple of times too - saying there is no X server.
    Before switching to systemd I never had any of these problems using the old rc.conf method. My DAEMONS array had the adsl service start after the network service.
    I need some help and advice to find out what is causing the problem and how to fix it.
    Last edited by bhrgunatha (2012-10-25 05:44:22)

    Thanks. That seems plausible. So I've been snooping at the journal.
    journalctl -ab
    Oct 25 17:06:13 starch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    Oct 25 17:06:14 starch systemd[1]: Started Recreate Volatile Files and Directories.
    Oct 25 17:06:14 starch systemd[1]: Starting System Initialization.
    Oct 25 17:06:14 starch systemd[1]: Reached target System Initialization.
    Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printing Service Sockets.
    Oct 25 17:06:14 starch systemd[1]: Listening on CUPS Printing Service Sockets.
    Oct 25 17:06:14 starch systemd[1]: Starting Console System Startup Logging...
    Oct 25 17:06:14 starch systemd[1]: Starting Restore Sound Card State...
    Oct 25 17:06:14 starch systemd[1]: Starting CUPS Printer Service Spool.
    Oct 25 17:06:14 starch systemd[1]: Started CUPS Printer Service Spool.
    Oct 25 17:06:14 starch systemd[1]: Starting D-Bus System Message Bus Socket.
    Oct 25 17:06:16 starch ntpd[381]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
    Oct 25 17:06:16 starch ntpd[413]: proto: precision = 0.156 usec
    Oct 25 17:06:17 starch ntpd[413]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Oct 25 17:06:17 starch ntpd[413]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Oct 25 17:06:18 starch ntpd[413]: Listen and drop on 1 v6wildcard :: UDP 123
    Oct 25 17:06:18 starch ntpd[413]: Listen normally on 2 lo 127.0.0.1 UDP 123
    Oct 25 17:06:18 starch ntpd[413]: Listen normally on 3 lo ::1 UDP 123
    Oct 25 17:06:18 starch ntpd[413]: peers refreshed
    Oct 25 17:06:18 starch ntpd[413]: Listening on routing socket on fd #20 for interface updates
    Oct 25 17:06:18 starch dbus[384]: [system] Activating systemd to hand-off: service name='org.freedesktop.ColorManager' unit='colord.service'
    Oct 25 17:06:18 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.systemd1'
    Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Oct 25 17:07:03 starch dbus[384]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
    Oct 25 17:07:03 starch dbus[384]: [system] Successfully activated service 'org.freedesktop.ColorManager'
    Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
    Oct 25 17:07:03 starch systemd[1]: Starting Manage, Install and Generate Color Profiles...
    Oct 25 17:07:03 starch systemd[1]: Started Manage, Install and Generate Color Profiles.
    Oct 25 17:07:03 starch systemd[1]: colord.service: main process exited, code=killed, status=6
    Oct 25 17:07:03 starch systemd[1]: Unit colord.service entered failed state.
    Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link down
    Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    Oct 25 17:07:04 starch kernel: PPP generic driver version 2.4.2
    Oct 25 17:07:04 starch cupsd[380]: Unknown directive DefaultAuthType on line 26.
    Oct 25 17:07:04 starch kernel: r8169 0000:02:00.0: eth0: link up
    Oct 25 17:07:04 starch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    Oct 25 17:07:04 starch pppoe-start[382]: TIMED OUT
    Oct 25 17:07:04 starch kernel: NET: Registered protocol family 24
    Oct 25 17:07:04 starch pppoe-start[382]: /usr/sbin/pppoe-start: line 193: 394 Terminated $CONNECT "$@" > /dev/null 2>&1
    That seems to confirm your theory.
    eth0 link is not up when attempting to start colord and adsl
    So the $64,000 question:
    How do I defer them until eth0 is ready?
    Or how can I force the eth0 link to be up before colord or adsl try to use it?
    Last edited by bhrgunatha (2012-10-25 01:33:36)

  • Systemd service failing on boot

    Hello, im new to Arch and systemd
    When I boot my computer the sabnzbd service fails to start, but if i start it manually afterwards it works fine.
    I can make it work by adding a 'sleep 10' to the .service file but that seems like a hack and I'd like to learn the correct way.
    It seems as though the sabnzbd.service is starting before the /run tmpfs partition has been mounted but I dont know. 
    I'm hoping someone smarter than me knows the answer to this
    Thanks
    Dave
    Below is the messages.log
    Oct 24 19:58:35 winter systemd[1]: PID file /run/sabnzbd/sabnzbd-8080.pid not readable (yet?) after start.
    Oct 24 19:58:36 winter systemd[1]: sabnzbd.service never wrote its PID file. Failing.
    Oct 24 19:58:36 winter systemd[1]: Unit sabnzbd.service entered failed state.
    Oct 24 19:58:36 winter systemd[1]: Starting Multi-User.
    Oct 24 19:58:36 winter systemd[1]: Reached target Multi-User.
    Oct 24 19:58:36 winter systemd[1]: Starting Graphical Interface.
    Oct 24 19:58:36 winter systemd[1]: Reached target Graphical Interface.
    Oct 24 19:58:36 winter systemd[1]: Starting Update UTMP about System Runlevel Changes...
    Oct 24 19:58:36 winter systemd[1]: Started Update UTMP about System Runlevel Changes.
    Oct 24 19:58:36 winter systemd[1]: Startup finished in 4s 330ms 255us (kernel) + 8s 66ms 514us (userspace) = 12s 396ms 769us.
    Oct 24 19:58:36 winter ifplugd[282]: Executing '/etc/ifplugd/netcfg.action eth0 up'.
    Oct 24 19:58:36 winter ifplugd[282]: client: up
    Oct 24 19:58:36 winter ifplugd[282]: client: loading ethernet-static
    Oct 24 19:58:36 winter ifplugd[282]: client: :: ethernet-static up [done]
    Oct 24 19:58:36 winter ifplugd[282]: Program executed successfully.
    sabnzbd.service:
    [Unit]
    Description=SABnzbd binary newsreader
    After=network.target
    [Service]
    EnvironmentFile=/etc/conf.d/sabnzbd_systemd
    #ExecStartPre=/usr/bin/sleep 10
    ExecStart=/bin/sh/ -c "python2 ${SABNZBD_DIR}/SABnzbd.py ${SABNZBD_ARGS} --pid /run/sabnzbd"
    ExecStop=/usr/bin/curl -f "${SABNZBD_PROTOCOL}://${SABNZBD_USPW}${SABNZBD_IP}:${SABNZBD_PORT}/sabnzbd/api?mode=shutdown&apikey=${SABNZBD_KEY}"
    Type=forking
    PIDFile=/run/sabnzbd/sabnzbd-8080.pid
    User=sabnzbd
    Group=sabnzbd
    [Install]
    WantedBy=multi-user.target

    For diagnostics try:
    # systemctl status sabnzbd.service

  • Systemd service conventions on package installation and removal

    If a package contains systemd service files, is there an expectation that the services are started/enabled during install and stopped/disabled during removal?

    No. Leave that to the user. The only thing that you may want to do is add a message to the install script's post_install function to remind the user.

  • [SOLVED] Dovecot Systemd Service Fails

    Hello all, I can't find the reason for why my dovecot fails. My journalctl doesn't provide output for the PID I give it.
    $ systemctl status dovecot.service
    * dovecot.service - Dovecot IMAP/POP3 email server
    Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled)
    Active: failed (Result: exit-code) since Mon 2014-08-04 17:53:27 UTC; 1min 4s ago
    Process: 4580 ExecStart=/usr/bin/dovecot -F (code=exited, status=89)
    Main PID: 4580 (code=exited, status=89)
    $ journalctl -b _PID=4580
    -- Logs begin at Fri 2013-03-29 01:07:20 UTC, end at Mon 2014-08-04 02:50:51 UTC. --
    Thank you for the help.
    ========================
    EDIT:
    ran the process described above: dovecot -F which gave me the dovecot error message. I had a misconfigured file (spelling mistake).
    Thanks for the help!
    Last edited by lexan (2014-08-04 18:11:28)

    Padfoot wrote:
    Try the following:
    [Unit]
    Description=K Display Manager
    Conflicts=[email protected]
    After=systemd-user-sessions.service [email protected]
    [Service]
    ExecStart=/usr/bin/kdm -nodaemon
    Restart=always
    IgnoreSIGPIPE=no
    StandardOutput=syslog
    [Install]
    Alias=display-manager.service
    Thank you for your suggestion. Unfortunately it does not work. Out of 4 boots, 3 time I ended up with blank screen. Interestingly, in the last boot I was able to switch to tty1 just after screen went blank and managed to log in to tty. I've restarted the kdm.service then manually in hope the image will be restored, but it wasn't. The restart of kdm then made the screen totally blank and I was unable to switch to tty anymore.
    Is it possible that radeon module in kernel has some slow initialization procedure and if X requires its services before it is properly initialized it ends up with blank screen?

  • [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)

  • Tip regarding the "systemd[1]: Failed to start Journal Service" error

    Just a tip regarding the well-known
    systemd[1]: Failed to start Journal Service
    error (which I ran into last weekend) to maybe save one or two among you a couple of hours of your time:
    The error is described here https://bbs.archlinux.org/viewtopic.php?id=151012 as well as in several other threads in other language boards / in other forums etc. It is usually (as in the linked thread) 'solved' by reinstalling the system - good old Windows magic, also useful when dealing with systemd.
    The Problem with this error is that you do not get into your system. Instead, systemd will print you the mentioned "Failed to start Journal Service" error message a couple of million times. There are also no logs that you could retrieve (when booting from a livesystem) and that would give you any helpful hints, since journal is systemd's logging service, old-style system logs are not kept, and the dmesg log doesn't survive the reboot with default settings.
    As pointed out in the above mentioned thread, you will see a few more instructive error messages when adding 'emergency' to the kernel line in the bootloader config.
    Now there may be plenty of reasons why the systemd journal service might not work. The most common and most annoying, however, appears to be this one:
    In this case you will see that the problem actually lies in
    systemd[1]: Cannot open /etc/machine-id: No such file or directory
    Now, 'man machine-id' reveals that "the /etc/machine-id file contains the unique machine id of the local system that is set during installation. (...) The machine ID is usually generated from a random source (...)". It is obviously perfectly justified to refuse to boot the system because an absolutely insignificant random number is missing. As far as systemd is concerned anyway.
    Usually, it seems, the /etc/machine-id is set by /usr/bin/systemd-machine-id-setup during installation or system upgrade. It is not documented anywhere that this is a rather important step and that you should better check if this was or was not actually done before rebooting. Obviously (but for no apparent reasons) systemd fails to run this (or to run this successfully) sometimes.
    Also to be recommended: Always retain (back up) your old kernel and initramfs and edit your bootloader config appropriately to be able to boot with your old kernel again ... just to have one or two options left to get back into the system in case of running into an unpleasant surprise from the side of systemd or other packages.
    The solution is, obviously, to create this file /etc/machine-id ... You probably want to do that from a livesystem (if you want to try it from the emergency shell, you would need to remount / (i.e. root) as rw and hope that systemd will not punish you for that) by just running the program that was designed for creating this file manually:  /usr/bin/systemd-machine-id-setup
    http://permalink.gmane.org/gmane.comp.s … devel/7528 states that it might also work with merely creating the file 'touch /etc/machine-id'. Though I didn't try that since I had enough fun with systemd for one week and didn't want to break my system again just to see if that works.

    Jristz wrote:
    ackalker wrote:Sorry for necrobumping this.
    Generating the machine-id in a consistent way is very important when working with KVM and containers, where the machine-id can be set for the VM or container. See `man systemd-machine-id-setup`.
    Again, _don't_ just put some random UUID in there, especially not in the systemd package install script, this makes provisioning Arch Linux containers a PITA.
    If you thing that the way that arch is handlynbg the machine-id is wrong or can be improved, then file a bug.
    He already did.
    Jristz wrote:Anyway, I thing if reinstalling systemd package or if systemd have a command to reinitialize the machine-id file.
    Like so many of your posts, I had to read this a half dozen times before it made any sense. I think you're hinting at the utility that ackalker already pointed out in the post you're replying to. And, if you read the install scriptlet, you wouldn't need to think about whether or not reinstalling would be an option. You would know that it isn't.

  • [solved] What makes systemd-logind.service fail?

    After last update made yesterday I was unable to reboot. With the help of an installation cd  and chrooting I disabled my graphical login manager lxdm which, when started, seems to do nothing and the system is stuck.
    Without lxdm service enabled, I can start xfce4 with
    startxfce4
    from commandline and everything seems to run fine. 
    But the booting process gives me several messages telling that the service systemd-logind failed. Apart from the virtual console created while booting and the one running X11 there is no other one (no login prompt when pressing strg+alt f3 e.g.)
    [root@amd64-archlinux ~]# systemctl status systemd-logind
    ● systemd-logind.service - Login Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
    Active: failed (Result: start-limit) since Sun 2014-06-08 19:09:24 CEST; 5min ago
    Docs: man:systemd-logind.service(8)
    man:logind.conf(5)
    http://www.freedesktop.org/wiki/Software/systemd/logind
    http://www.freedesktop.org/wiki/Software/systemd/multiseat
    Process: 336 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
    Main PID: 336 (code=exited, status=1/FAILURE)
    Status: "Shutting down..."
    Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
    Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
    Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
    Jun 08 19:09:24 amd64-archlinux systemd[1]: Stopping Login Service...
    Jun 08 19:09:24 amd64-archlinux systemd[1]: Starting Login Service...
    Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
    Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
    Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
    Has anyone an idea where to lead me?
    Last edited by bernd_b (2014-06-09 11:20:21)

    I don't know if I got you point - but here is a try:
    I am running X11 started manually with "startxfce4". So firing up a konsole in X11 I do and get
    root@amd64-archlinux pkg]# systemctl stop systemd-logind
    [root@amd64-archlinux pkg]# systemctl start systemd-logind
    Job for systemd-logind.service failed. See 'systemctl status systemd-logind.service' and 'journalctl -xn' for details.
    journalctl -xn:
    -- Unit systemd-logind.service has begun shutting down.
    Jun 08 21:38:18 amd64-archlinux systemd[1]: Starting Login Service...
    -- Subject: Unit systemd-logind.service has begun with start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-logind.service has begun starting up.
    Jun 08 21:38:18 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
    Jun 08 21:38:18 amd64-archlinux systemd[1]: Failed to start Login Service.
    -- Subject: Unit systemd-logind.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit systemd-logind.service has failed.
    -- The result is failed.
    I ran the service directly I get:
    [root@amd64-archlinux pkg]# /usr/lib/systemd/systemd-logind
    Failed to connect to system bus: No such file or directory
    Failed to fully start up daemon: No such file or directory
    What I figured out so far is this in addition:
    - krusader does not start- there is no response or message in the konsole when firing up this application.
    - I can only mount nfs-shares with the option "-o nolock" otherwise I get, e.g.
    mount.nfs: rpc.statd is not running but is required for remote locking.
    mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
    mount.nfs: an incorrect mount option was specified
    Last edited by bernd_b (2014-06-08 19:48:43)

  • Systemd-remount-fs.service fails [SOLVED]

    After a fresh install on a brandnew laptop, my root partition is being mounted read only, and I see that systemd-remount-fs.service fails:
    [root@anton ~]# systemctl status systemd-remount-fs.service
    systemd-remount-fs.service - Remount Root and Kernel File Systems
    Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
    Active: failed (Result: exit-code) since Sat, 2012-12-01 21:00:05 MST; 18min ago
    Docs: man:systemd-remount-fs.service(8)
    Process: 186 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/system/systemd-remount-fs.service
    Dec 01 21:00:05 anton systemd-remount-fs[186]: mount: / not mounted or bad option
    Dec 01 21:00:05 anton systemd-remount-fs[186]: In some cases useful info is found in syslog - try
    Dec 01 21:00:05 anton systemd-remount-fs[186]: dmesg | tail or so
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    I have no idea why this is happening, or what to do to try and fix it - any help/advice would be greatly appreciated.  Following is the information I think is necessary for assistance:
    Note that I have /usr on a separate partition, which I suspect is possibly involved in the issue somehow.
    Here's my fstab:
    [root@anton ~]# cat /etc/fstab
    # /dev/sda5
    #UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 defaults,rw,noatime,discard,data=writeback 0 1
    # /dev/sda6
    UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,noatime,discard,data=writeback 0 0
    # /dev/sda7
    UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
    # /dev/sda8
    UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
    Here's the relevant output from mount (note that my root (sda5) partition is not being mount with the options I specified in fstab):
    [root@anton ~]# mount | grep sda
    /dev/sda5 on / type ext4 (ro,relatime,data=ordered)
    /dev/sda6 on /usr type ext4 (rw,noatime,discard,data=writeback)
    /dev/sda7 on /var type ext4 (rw,noatime,discard,data=ordered)
    /dev/sda8 on /home type ext4 (rw,relatime,discard,data=ordered)
    Relavant snippet from /boot/grub/grub.cfg:
    menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-a09ff37e-ce60-4173-b95a-4b71a53c01d3' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 a09ff37e-ce60-4173-b95a-4b71a53c01d3
    else
    search --no-floppy --fs-uuid --set=root a09ff37e-ce60-4173-b95a-4b71a53c01d3
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 ro init=/usr/lib/systemd/systemd
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux.img
    Finally, here's my mkinitcpio.cfg:
    [root@anton ~]# cat /etc/mkinitcpio.conf
    MODULES=""
    BINARIES=""
    FILES=""
    HOOKS="base udev autodetect sata filesystems usbinput usr fsck shutdown"
    Last edited by corey_s (2012-12-02 08:57:35)

    Thanks for the quick response, WonderWoofy ( by the way, great username! )!
    When I removed or modified the the mount options in the bootloader kernel command line, there was no change to the status of the fs after boot-up. I had changed it at one point from 'ro', to 'rw'; but doing so had no affect on the output of the mount command.
    However, I did finally identify the cause:  turns out if I specify 'data=writeback', in fstab for the root partition, then systemd-remount-fs.service fails, as per my OP - leaving me with a 'ro'-mounted root filesystem. Simply removing that, or changing it to 'data=ordered', solved the issue: when I rebooted, the root partition was mounted as per my fstab config.
    So, my fstab now looks like this:
    # /dev/sda5
    UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 rw,noatime,discard 0 1
    # /dev/sda6
    UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,ro,noatime,discard,data=writeback 0 0
    # /dev/sda7
    UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
    # /dev/sda8
    UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
    ... and all is now well.
    I'll mark this as solved, but I'll also ask:  why does specifying 'data=writeback' on my root partition cause the systemd-remount-fs.service to fail? Any experts out there know?
    Last edited by corey_s (2012-12-02 06:46:32)

  • [SOLVED]systemd-tmpfiles-setup.service fails

    Hi,
    I have installed arch on an old laptop (dell inspiron 6000). I haven't used arch linux for last 2 years. It seems system management style has changed drastically.
    Anyways, systemctl status systemd-tmpfiles-setup.service returns this;
    ● 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 Sal 2015-06-09 11:00:18 EEST; 38min ago
    Docs: man:tmpfiles.d(5)
    man:systemd-tmpfiles(8)
    Process: 228 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
    Main PID: 228 (code=exited, status=1/FAILURE)
    Haz 09 11:00:18 yasar-laptop systemd[1]: Starting Create Volatile Files and Directories...
    Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
    Haz 09 11:00:18 yasar-laptop systemd[1]: Failed to start Create Volatile Files and Directories.
    Haz 09 11:00:18 yasar-laptop systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
    Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service failed.
    Is this something that I should be concerned? I don't really know what this service supposed to do?
    If I should be concerned, how to troubleshoot it? Keep in mind that this is a fresh arch install.
    Last edited by yasar11732 (2015-06-09 16:31:04)

    Thanks,
    I have add acl option to fstab file, it works now. If anyone else has this problem, here is how my fstab file looks now;
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    UUID=936297ec-2bc3-45ef-bdb0-0a4ce7239204 / ext4 rw,relatime,data=ordered 0 1
    UUID=d1fd9d31-99b5-45ba-97f4-a4c20b96e48b /var reiserfs rw,relatime,acl 0 2
    UUID=6a9b3e39-8ea2-446f-9a71-79faab7cdafe /home xfs rw,relatime,attr2,inode64,noquota 0 2
    # UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4
    UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4 none swap defaults 0 0

  • RCU Installation - Service Name of fresh DB installation

    Hi,
    I am setting up SOA suite 11g. I have Oracle 11.1.0.7 DB (fresh installation) and I my lsnrctl is showing following information;
    $ lsnrctl status
    LSNRCTL for IBM/AIX RISC System/6000: Version 11.1.0.7.0 - Production on 08-SEP-2010 17:05:49
    Copyright (c) 1991, 2008, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for IBM/AIX RISC System/6000: Version 11.1.0.7.0 - Production
    Start Date 08-SEP-2010 15:42:00
    Uptime 0 days 1 hr. 23 min. 49 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP ON
    Listener Log File /home/oracle/Oracle11gR1/app/oracle/product/11.1.0/db_1/log/diag/tnslsnr/hml-bladep6a2/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hml-bladep6a2)(PORT=1521)))
    The listener supports no services
    The command completed successfully
    I chose to create new repository and provided following information on RCU setup screen;
    Host Name: IP_Address of the machine
    Port: 1521
    Service Name: *<--- I dont know what to provide here as I didn't create any databases on server yet*
    Username: sys
    Password: ******
    Role: sysdba
    Am I missing anything....?

    Hi,
    I found the solution and some more useful information which I wanted to add here for future reference.
    To run RCU, we need to create a DB first in Oracle and then LSNRCTL will pick up that database and start listening on default port (1521). Use you DB name as Service name which can be verified as follows;
    LSNRCTL Status_
    $ lsnrctl status
    LSNRCTL for IBM/AIX RISC System/6000: Version 11.1.0.7.0 - Production on 14-SEP-2010 09:33:34
    Copyright (c) 1991, 2008, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for IBM/AIX RISC System/6000: Version 11.1.0.7.0 - Production
    Start Date 13-SEP-2010 16:12:15
    Uptime 0 days 17 hr. 21 min. 18 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP ON
    Listener Log File /home/oracle/Oracle11gR1/app/oracle/product/11.1.0/db_1/log/diag/tnslsnr/hml-bladep6a2/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hml-bladep6a2)(PORT=1521)))
    Services Summary...
    Service "AIA" has 1 instance(s).
    Instance "AIA", status READY, has 1 handler(s) for this service...
    Service "AIA_XPT" has 1 instance(s).
    Instance "AIA", status READY, has 1 handler(s) for this service...
    The command completed successfully
    Also I found out during my RCU installation we need some more settings before and after creating DB to run RCU successfully;
    *1) DB_BLOCK_SIZE Settings*
    The default initDB_NAME.ora file create DB with *'db_block_size=4096'*, if that the case you'll see following error while installing RCU;
    RCU-6002:The specified database does not meet the minimum requirement to load metadata repository.
    RCU-6080:Global prerequisite check failed - Check requirement for specified database
    RCU-6107:DB Init Param Prerequisite failure for: DB_BLOCK_SIZE
    Current Value is 4 KB. It should be greater than or equal to 8 KB.
    User should have sysdba or dba privilages.
    It is irreversible :(. You have to drop and create DB again with following parameter in $ORACLE_HOME/dbs/initDB_NAME.ora file;
    db_block_size=8192
    *2) User Previlages*
    You can not use SYS/SYSDBA to connect to Oracle DB from RCU setup. To grant SYSDBA permissions to the ORACLE DB user first apply following command from shell;
    $ orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=PASSWORD entries=4 force=y
    Note: In above command the password is Unix/Windows login password not SYS password.
    Now, login into SQLPLUS prompt using sys/sysdba to finally grant SYSDBA opermission to normal Oracle DB User as follows and restart DB to apply changes;
    SQL> grant sysdba to aia;     <-- Grant SYSDBA permission to user 'aia' in this case
    Grant succeeded.
    SQL> grant dba to aia;
    Grant succeeded.
    SQL> startup force;
    ORA-32004: obsolete and/or deprecated parameter(s) specified
    ORACLE instance started.
    Total System Global Area 1286144000 bytes
    Fixed Size 2153376 bytes
    Variable Size 738198624 bytes
    Database Buffers 536870912 bytes
    Redo Buffers 8921088 bytes
    Database mounted.
    Database opened.
    Hope above information will help.
    SJunejo

  • Installation issue : sql server 2008 r2 some services failed to installed on windows 7

    I have been facing this problem while installing sql server 2008 r2.. i tried so many times but same result .. it shows sql server installed with some errors
    database engine service : failed
    SQL Server Replication : failed
    Full-Text Search : failed
    Analysis Services : failed
    Reporting Services : failed
    And my Log file (or) summary file is (it is in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log):
    Overall summary:
      Final result:                  User cancelled
      Exit code (Decimal):           -2068380094
      Exit facility code:            1207
      Exit error code:               1602
      Exit message:                  User has cancelled.
      Start time:                    2014-08-14 21:15:26
      End time:                      2014-08-14 21:23:58
      Requested action:              AddNode
    Machine Properties:
      Machine name:                  MANJU-PC
      Machine processor count:       4
      OS version:                    Windows Vista
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services                
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication                  
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search                        
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services                       
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services                      
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Management Tools - Basic                 1033                 Developer Edition   
    10.0.1600.22    No        
      Sql Server 2008                                                         
    Management Tools - Complete              1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Connectivity                1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Backwards Compatibility     1033                 Developer Edition    10.0.1600.22    No      
      Sql Server 2008                                                         
    Client Tools SDK                         1033                
    Developer Edition    10.0.1600.22    No        
      Sql Server 2008                                                         
    Integration Services                     1033                 Developer Edition   
    10.0.1600.22    No        
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\x86\setup\
      Installation edition:          DEVELOPER
    User Input Settings:
      ACTION:                        AddNode
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                *****
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      CONFIGURATIONFILE:             
      FAILOVERCLUSTERGROUP:          
      FAILOVERCLUSTERNETWORKNAME:    <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTANCENAME:                  <empty>
      MEDIASOURCE:                   D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                *****
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\ConfigurationFile.ini
    Detailed results:
      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\SystemConfigurationCheck_Report.htm
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
        Message:
            User has cancelled.
        Stack:
            at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
            at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

      Requested action:              AddNode
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services                
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication                  
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search                        
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services                       
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services                      
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Management Tools - Basic                 1033                 Developer Edition   
    10.0.1600.22    No        
      Sql Server 2008                                                         
    Management Tools - Complete              1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Connectivity                1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Backwards Compatibility     1033                 Developer Edition    10.0.1600.22    No      
      Sql Server 2008                                                         
    Client Tools SDK                         1033                
    Developer Edition    10.0.1600.22    No        
      Sql Server 2008                                                         
    Integration Services                     1033                 Developer Edition   
    10.0.1600.22    No        
    Instead of installing SQL server instance you selected add node which is to be selected when SQL server installation is to be made on Node which is being added to cluster. Since your OS is not clustered I am sure you selected worng option.
    Please right click on setup file and select run as administrator. Now installation window which pops up on that on left hand side select
    installation and then on page that appears select 'New server standalone installation or add feature to existing installation'.
    You already have SQL server 2008 installed on your machine as per feature discovery report
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • I'm installing the newest itunes 64 bit on my win 7 64 bit professional os. using the itunes installer it loads itunes part way and then i get an error message saying that bonjour service failed to start. i cant get itunes any further. i have to back out

    I'm installing the newest version of Itunes over the last version on my laptop. win 7 pro os. it starts the install then a error msg comes up stating that Bonjour service failed to start. verify that i have sufficient priveleges to start system services. I can't retry, ignore only cancel which un-installs all that it has installed and reverts me to the last version which i had. any idea?

    it starts the install then a error msg comes up stating that Bonjour service failed to start. verify that i have sufficient priveleges to start system services.
    Sometimes we can get past that one by disabling the Bonjour Service prior to the install.
    In your Start menu, right-click Computer and select "Manage".
    Expand "Services & Applications".
    Open "Services". (Perhaps maximise the screen to better see what's going on.)
    Right-click the Bonjour Service and select "Properties".
    In the General tab, set the Startup type to "Disabled":
    ... and click OK.
    Restart the PC and try another iTunes install. Does it go through properly this time?

  • Error during iTunes 10 installation - iPod Service failed to start

    Hi Everyone,
    I am getting this error during installation of iTunes 10(Windows XP).
    +*"Service (iPod Service)failed to start.Verify that you have sufficient priveleges to start system services."*+
    *Can any of you please help?* I ignored it first and continued with the installation. Then tried to update iphone to iOS 4.1 which crashed. I had to go to Apple store to get my iphone restored. I am having trouble installing itunes and cannot restore data from backup.
    I tried uninstalling itunes and deleted all itunes data as suggested by the guy at the Apple store. Still not working. Will appreciate if someone can help resolve this error. Thanks.

    I just got off the phone with Apple tech support. The problem with that iPod Service is a problem with XP Service Pack 3, but can be fixed this way:
    1. Right click on "My Computer", select "Properties"
    2. Click on the Advanced tab.
    3. in the Startup and Recovery section, click the Settings button.
    4. Click the Edit byutton to edit your boot.ini file in notepad.
    5. Look for "/noexecute=" in the file and change the word after the equals to "optin" (sorry - I don't remember what the original setting was anymore).
    6. Save the file, close notepad, click the OK button on Startup and Recovery window, then reboot.
    The warning message about the iPod Service should stop. Also, this helps with iPhones that are not recognized by Windows or iTunes after an install fails.

Maybe you are looking for