Systemd-update-utmp.services wastes 16.990s while booting.

Info:
uname -a
Linux arch-linux-desk 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64 GNU/Linux
lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 4
Model name: AMD Phenom(tm) II X4 965 Processor
Stepping: 3
CPU MHz: 3816.867
BogoMIPS: 7636.80
Virtualization: AMD-V
L1d cache: 64K
L1i cache: 64K
L2 cache: 512K
L3 cache: 6144K
NUMA node0 CPU(s): 0-3
journalctl -u system-update-utmp
-- Reboot --
Mar 01 19:00:28 arch-linux-desk systemd[1]: Merged into installed job systemd-update-utmp.service/start as 51
Mar 01 19:00:48 arch-linux-desk systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
Mar 01 19:00:48 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp reboot
Mar 01 19:00:48 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 532
Mar 01 19:00:48 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> start
Mar 01 19:00:48 arch-linux-desk systemd[532]: Executing: /usr/lib/systemd/systemd-update-utmp reboot
Mar 01 19:00:48 arch-linux-desk systemd[1]: Child 532 belongs to systemd-update-utmp.service
Mar 01 19:00:48 arch-linux-desk systemd[1]: systemd-update-utmp.service: main process exited, code=exited, status=0/SUCCESS
Mar 01 19:00:48 arch-linux-desk systemd[1]: systemd-update-utmp.service changed start -> exited
Mar 01 19:00:48 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/start finished, result=done
Mar 01 19:00:48 arch-linux-desk systemd[1]: Started Update UTMP about System Reboot/Shutdown.
Mar 01 19:29:41 arch-linux-desk systemd[1]: Installed new job systemd-update-utmp.service/stop as 2431
Mar 01 19:29:44 arch-linux-desk systemd[1]: Stopping Update UTMP about System Reboot/Shutdown...
Mar 01 19:29:44 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp shutdown
Mar 01 19:29:44 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 20268
Mar 01 19:29:44 arch-linux-desk systemd[1]: systemd-update-utmp.service changed exited -> stop
Mar 01 19:29:44 arch-linux-desk systemd[20268]: Executing: /usr/lib/systemd/systemd-update-utmp shutdown
Mar 01 19:29:45 arch-linux-desk systemd[1]: Child 20268 belongs to systemd-update-utmp.service
Mar 01 19:29:45 arch-linux-desk systemd[1]: systemd-update-utmp.service: control process exited, code=exited status=0
Mar 01 19:29:45 arch-linux-desk systemd[1]: systemd-update-utmp.service got final SIGCHLD for state stop
Mar 01 19:29:45 arch-linux-desk systemd[1]: systemd-update-utmp.service changed stop -> dead
Mar 01 19:29:45 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/stop finished, result=done
Mar 01 19:29:45 arch-linux-desk systemd[1]: Stopped Update UTMP about System Reboot/Shutdown.
-- Reboot --
Mar 01 19:31:00 arch-linux-desk systemd[1]: Merged into installed job systemd-update-utmp.service/start as 52
Mar 01 19:31:03 arch-linux-desk systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
Mar 01 19:31:03 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp reboot
Mar 01 19:31:03 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 550
Mar 01 19:31:03 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> start
Mar 01 19:31:03 arch-linux-desk systemd[550]: Executing: /usr/lib/systemd/systemd-update-utmp reboot
Mar 01 19:31:03 arch-linux-desk systemd[1]: Child 550 belongs to systemd-update-utmp.service
Mar 01 19:31:06 arch-linux-desk systemd[1]: systemd-update-utmp.service: main process exited, code=exited, status=0/SUCCESS
Mar 01 19:31:20 arch-linux-desk systemd[1]: systemd-update-utmp.service changed start -> exited
Mar 01 19:31:20 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/start finished, result=done
Mar 01 19:31:20 arch-linux-desk systemd[1]: Started Update UTMP about System Reboot/Shutdown.
Mar 01 19:36:32 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 01 21:54:04 arch-linux-desk systemd[1]: Installed new job systemd-update-utmp.service/stop as 1797
Mar 01 21:54:07 arch-linux-desk systemd[1]: Stopping Update UTMP about System Reboot/Shutdown...
Mar 01 21:54:07 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp shutdown
Mar 01 21:54:07 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 11234
Mar 01 21:54:07 arch-linux-desk systemd[1]: systemd-update-utmp.service changed exited -> stop
Mar 01 21:54:07 arch-linux-desk systemd[11234]: Executing: /usr/lib/systemd/systemd-update-utmp shutdown
Mar 01 21:54:07 arch-linux-desk systemd[1]: Child 11234 belongs to systemd-update-utmp.service
Mar 01 21:54:07 arch-linux-desk systemd[1]: systemd-update-utmp.service: control process exited, code=exited status=0
Mar 01 21:54:07 arch-linux-desk systemd[1]: systemd-update-utmp.service got final SIGCHLD for state stop
Mar 01 21:54:07 arch-linux-desk systemd[1]: systemd-update-utmp.service changed stop -> dead
Mar 01 21:54:07 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/stop finished, result=done
Mar 01 21:54:07 arch-linux-desk systemd[1]: Stopped Update UTMP about System Reboot/Shutdown.
-- Reboot --
Mar 02 16:06:04 arch-linux-desk systemd[1]: Merged into installed job systemd-update-utmp.service/start as 52
Mar 02 16:06:09 arch-linux-desk systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
Mar 02 16:06:09 arch-linux-desk systemd[1]: About to execute: /usr/lib/systemd/systemd-update-utmp reboot
Mar 02 16:06:09 arch-linux-desk systemd[1]: Forked /usr/lib/systemd/systemd-update-utmp as 526
Mar 02 16:06:09 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> start
Mar 02 16:06:09 arch-linux-desk systemd[526]: Executing: /usr/lib/systemd/systemd-update-utmp reboot
Mar 02 16:06:09 arch-linux-desk systemd[1]: Child 526 belongs to systemd-update-utmp.service
Mar 02 16:06:11 arch-linux-desk systemd[1]: systemd-update-utmp.service: main process exited, code=exited, status=0/SUCCESS
Mar 02 16:06:26 arch-linux-desk systemd[1]: systemd-update-utmp.service changed start -> exited
Mar 02 16:06:26 arch-linux-desk systemd[1]: Job systemd-update-utmp.service/start finished, result=done
Mar 02 16:06:26 arch-linux-desk systemd[1]: Started Update UTMP about System Reboot/Shutdown.
Mar 02 16:33:59 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:11 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:24 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:37 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:46 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:34:58 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:35:02 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
Mar 02 16:51:11 arch-linux-desk systemd[1]: systemd-update-utmp.service changed dead -> exited
systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @43.083s
└─multi-user.target @43.082s
└─spamassassin.service @31.838s +11.243s
└─network.target @31.831s
└─NetworkManager.service @27.053s +4.774s
└─basic.target @26.943s
└─timers.target @26.934s
└─systemd-tmpfiles-clean.timer @26.934s
└─sysinit.target @26.870s
└─systemd-update-utmp.service @9.874s +16.990s
└─systemd-tmpfiles-setup.service @9.287s +577ms
└─local-fs.target @9.278s
└─tmp.mount @9.118s +155ms
└─local-fs-pre.target @1.972s
└─systemd-tmpfiles-setup-dev.service @1.567s +397ms
└─kmod-static-nodes.service @686ms +872ms
└─systemd-journald.socket @648ms
└─-.mount @647ms
└─system.slice @1.069s
└─-.slice @1.061s
Last edited by 814ckf0x (2014-03-02 18:03:00)

Okay.  For reference, that step takes 0.055 seconds on my box.
ewaller$@$odin ~ 1002 %systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @24.443s
`-multi-user.target @24.443s
`-postfix.service @21.770s +2.672s
`-network.target @21.768s
`[email protected] @11.892s +9.876s
`-basic.target @11.062s
`-timers.target @11.059s
`-systemd-tmpfiles-clean.timer @11.059s
`-sysinit.target @11.059s
`-systemd-update-utmp.service @11.003s +55ms
`-systemd-tmpfiles-setup.service @10.904s +98ms
`-local-fs.target @10.903s
`-home.mount @10.750s +152ms
`-systemd-fsck@dev-disk-by\x2duuid-1e70da27\x2d41c7\x2d4
`-dev-disk-by\x2duuid-1e70da27\x2d41c7\x2d43fc\x2d963b
ewaller$@$odin ~ 1003 %
I think you should look through your journal for more information.  You may want to pastebin it and post a link here.

Similar Messages

  • [SOLVED] Problems with systemd-update-utmp after systemd update

    Hi all,
    I noticed that systemd-update-utmp-runlevel.service has been failing since the last systemd update. My systemd is:
    Repository : core
    Name : systemd
    Version : 184-2
    $ systemctl status systemd-update-utmp-runlevel.service
    systemd-update-utmp-runlevel.service - Update UTMP about System Runlevel Changes
    Loaded: loaded (/usr/lib/systemd/system/systemd-update-utmp-runlevel.service; static)
    Active: failed (Result: exit-code) since Sat, 02 Jun 2012 13:55:40 +0200; 56min ago
    Docs: man:utmp(5)
    Main PID: 395 (code=exited, status=1/FAILURE)
    CGroup: name=systemd:/system/systemd-update-utmp-runlevel.service
    The exact cause of error is:
    Jun 02 13:55:40 arch systemd-update-utmp[395]: Failed to write utmp record: No such file or directory
    Jun 02 13:55:40 arch systemd[1]: systemd-update-utmp-runlevel.service: main process exited, code=exited, status=1
    What's more, after this update I am not able to mount vmware hgfs shares. I've got following entry in my /etc/fstab (from arch's wiki)
    #enable shared folders
    .host:/ /mnt/hgfs vmhgfs defaults,ttl=5 0 0
    It worked just fine. After the update system boots into maintenance mode with the following message found in sysemd-journal:
    arch mount[143]: Directory in share name must not be empty
    arch mount[143]: Error: share name is invalid, aborting mount
    After commenting hgfs mount entry out the system boots normally.
    Thanks in advance.
    EDIT:
    Mounting hgfs shares manually works as expected
    $: sudo mount /mnt/hgfs
    Could not add entry to mtab, continuing
    mtab:
    .host:/ /mnt/hgfs vmhgfs rw,relatime 0 0
    so this issue must be systemd related
    Last edited by mrzeznicki (2012-06-07 15:18:05)

    falconindy wrote:Still can't reproduce this. libmount's parser does just fine with ".host" as a dummy entry in my /etc/hosts file mapped for an NFS share.
    Yep, libmount is probably not a problem, I guess this error comes from vmware's hgfsmounter
    static Bool
    ParseShareName(const char *shareName, // IN: Share name to validate
    const char **shareNameHost, // OUT: Share name, host component
    const char **shareNameDir) // OUT: Share name, dir component
    const char *colon, *dir;
    /* 1) Must be colon separated into host and dir. */
    colon = strchr(shareName, ':');
    if (colon == NULL) {
    printf("Share name must be in host:dir format\n");
    return FALSE;
    /* 2) Dir must not be empty. */
    dir = colon + 1;
    if (*dir == '\0') {
    printf("Directory in share name must not be empty\n");
    return FALSE;
    /* 3) Dir must start with forward slash. */
    if (*dir != '/') {
    printf("Directory in share name must be an absolute path\n");
    return FALSE;
    /* 4) Host must be ".host". */
    if (strncmp(shareName, ".host:", 6) != 0) {
    printf("Host in share name must be \".host\"\n");
    return FALSE;
    *shareNameHost = ".host";
    LOG("Host component of share name is \"%s\"\n", *shareNameHost);
    *shareNameDir = dir;
    LOG("Directory component of share name is \"%s\"\n", *shareNameDir);
    return TRUE;
    I am just wondering why it worked before (and why manual mount works). Is there anything in systemd mount layer that consumes '/'?

  • Systemd-udev-settle.service suddenly active after last system update

    Hi,
    with my last pacman -Syu I noticed that my boot time went up from 4s to 8s.
    Using systemd-analyze, I saw that systemd-udev-settle.service is the culprit.
    I am not using lvm or similar, so AFAIK systemd-udev-settle.service should not be running on my system.
    Does anybody know why this was activated by the last system update and if it is safe to just mask or disable the unit?
    With best regards,
    p90

    I noticed that it is slowing down my boot also, I checked and for some reason the lvm2 package was installed which looks like it was partially causing it. It has a couple messages at boot and in dmesg. I removed lvm2 and by boot time is a little better, and masking systemd-udev-settle brings my boot back to where it should be.
    Last edited by Kopkins (2014-11-11 15:55:33)

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

  • [SOLVED] systemd and ntpd.service

    I've just converted to pure systemd according to the wiki. Everything went remarkably well, with just a little blemish. While I'm not notified of any error at startup, when I check systemctl I find that ntpd.service's LOAD/ACTIVE/SUB is loaded/failed/failed.
    systemctl status ntpd.service gives me this:
    ntpd.service - Network Time Service
    Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled)
    Active: failed (Result: exit-code) since Thu, 18 Oct 2012 04:16:56 +0200; 6s ago
    Process: 1397 ExecStart=/usr/bin/ntpd -g -u ntp:ntp (code=exited, status=0/SUCCESS)
    Main PID: 1398 (code=exited, status=255)
    CGroup: name=systemd:/system/ntpd.service
    Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
    Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
    Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
    and journalctl pretty much more of the same:
    Oct 18 04:16:56 mike ntpd[1397]: ntpd [email protected] Tue Aug 21 15:06:24 UTC 2012 (1)
    Oct 18 04:16:56 mike ntpd[1398]: proto: precision = 0.106 usec
    Oct 18 04:16:56 mike ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
    Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
    Oct 18 04:16:56 mike sudo[1394]: pam_unix(sudo:session): session closed for user root
    Oct 18 04:16:56 mike ntpd[1398]: Listen and drop on 1 v6wildcard :: UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 2 lo 127.0.0.1 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 3 eth0 192.168.0.2 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 4 lo ::1 UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: Listen normally on 5 eth0 fe80::224:1dff:fec4:aebe UDP 123
    Oct 18 04:16:56 mike ntpd[1398]: peers refreshed
    Oct 18 04:16:56 mike ntpd[1398]: Listening on routing socket on fd #22 for interface updates
    Oct 18 04:16:56 mike systemd[1]: Started Network Time Service.
    Oct 18 04:16:56 mike systemd[1]: ntpd.service: main process exited, code=exited, status=255
    Oct 18 04:16:56 mike systemd[1]: Unit ntpd.service entered failed state.
    Trying to use it manually (eg. ntpd -qg) works, so I'm not sure what's wrong with it exactly. Where else should I look?
    Last edited by Mr_Mario (2012-12-06 11:29:57)

    slickvguy wrote:I've just started converting to systemd and ran into the same issue. I believe the problem is that you are missing the ntp group from your group file. If you updated your system and merely renamed your group.pacnew to group, it no longer contains the ntp group that was previously added. I just added the ntp group again ( ntp:x:87: ), and ntp started properly and the status is correct. Hope this helps.
    That was it. Thank you!

  • Get-mailboxdatabasecopystatus -identity DBNAME | fl gives errors "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for". DB is mounted and the DB copies are in healthy status.

    We are getting a SCOM alert " Database copy isn''''t keeping up with the changes on the active database copy and has failed."
    When we go to the mailbox server and check we found all the Mailbox DB's are mounted properly and their copies are in healthy state. Further digging to this problem we found that there are no critical events to this DB in the eventviewer.
    When we runt he get-mailboxdatabasecopystatus -identity DBNAME | Fl then in the ErrorMessage section we get error "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for . If the copy doesn't
    recover automatically, administrator intervention may be necessary. Error: The directory is not empty."
    ErrorEventID : 4126
    In the event viewer we get a Information event 4114 saying the DB redundancy health check passed and in the details section we get the same error message mentioned above.
    Also we observed that the "MSExchange Replication" counter "Failed" is set to 1 for this perticular DB but is is set to 0 for the other DB's. Tried restarting the MSEXChange replication service but still the "Failed" counter
    is 1 and the SCOM alert is still active.
    The version is Exchange 2010 SP3 UR5
    Any clues???

    Hi,
    From your description, this issue only affect one mailbox datatabase.
    Please use the Update-MailboxDatabaseCopy command to check result.
    If it doesn't work, please dismount your active database copy and check if this is Clean Shutdown, if it's dirty shutdown, please bring to clean shutdown and mount this database copy. Then run the Update-MailboxDatabaseCopy command again to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

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

  • The event logging service encountered an error while processing an incoming event published from Microsoft-Windows-Security-Auditing.

    Last night, some of our systems installed updates released on 11/13/2014.  
    KB3021674
    KB2901983
    KB3023266
    KB3014029
    KB3022777
    KB3020388
    KB890830
    Today, all of the servers running Windows Server 2008 R2 started logging the following error in the Security log over and over:
    Log Name:      Security
    Source:        Microsoft-Windows-Eventlog
    Date:          1/15/2015 11:12:39 AM
    Event ID:      1108
    Task Category: Event processing
    Level:         Error
    Keywords:      Audit Success
    User:          N/A
    Description:
    The event logging service encountered an error while processing an incoming event published from Microsoft-Windows-Security-Auditing.
    Servers running Windows Server 2008 that also installed the updates are not experiencing the problem.  It looks like one of the updates may have introduced this problem with Server 2008 R2.

    ...Did you for sure confirm that:
    https://technet.microsoft.com/library/security/MS15-001
    is the cause?
    I did.  I had a VM that was not experiencing the problem.  I took a snapshot and tested the patches one by one.  Installing only KB3023266 immediately caused the issue to occur (after reboot).  A similar process was used to confirm that
    installing KB2675611 resolved the problem.
    Note that I found the installation of KB2675611 is usually quick, but it took several hours hours to install on some of our systems.  We had installed this patch a few months ago on a couple of servers and it was always quick to install.  But,
    it seems like installing it on a symptomatic system can cause it to take a long time.

  • [SOLVED] error after lastest systemd update

    After latest updates I get this message while booting:
    systemd-udevd[137]: error opening ATTR{/sys/devices/pci0000:00/0000:00:1a.1/usb2/2-1/2-1:1.0/power/control} for writing: No such file or directory
    which is due there is no file /sys/devices/pci0000:00/0000:00:1a.1/usb2/2-1/2-1:1.0/power/control, the directory is there but no file 'control'.
    Is this a bug?
    Thanks in advance!
    solved with last update
    Last edited by miro279 (2014-03-19 10:44:15)

    Thanks it worked. Now I only have to stress about what game I'm going to play

  • Planner group is not updated in service notification using BAPI

    Hi,
    Planner group is not updated in service notification using BAPI BAPI_ALM_ORDER_MAINTAIN.
    I have written the below code, but planner group is not updated in the service notification.
    Please advice which parameters do i need to pass to update planner group in the service notification.
              wa_methods-refnumber      = '000001'.
              wa_methods-objecttype     = 'PARTNER'.
              wa_methods-method         = 'CREATE'.
              wa_methods-objectkey      = wa_subscr1-aufnr.
              APPEND wa_methods TO i_methods.
              wa_methods-refnumber      = '000002'.
              wa_methods-objecttype     = 'HEADER'.
              wa_methods-method         = 'CREATE'.
              wa_methods-objectkey      = wa_subscr1-aufnr.
              APPEND wa_methods TO i_methods.
              wa_methods-refnumber      = '000000'.
              wa_methods-objecttype     = ' '.
              wa_methods-method         = 'SAVE'.
              APPEND wa_methods TO i_methods.
              REFRESH i_partner.
              CLEAR wa_partner.
              wa_partner-orderid        = wa_subscr1-aufnr.
              wa_partner-partn_role     = 'VW'.
              wa_partner-partn_role_old = ''.
              wa_partner-partner        = wa_subscr1-parnr.
              wa_partner-partner_old    = ''.
              APPEND wa_partner TO i_partner.
              REFRESH i_planrgrp.
              CLEAR wa_planrgrp.
              wa_planrgrp-orderid        = wa_subscr1-aufnr.
              wa_planrgrp-plangroup      = wa_subscr1-ingpr.
              APPEND wa_planrgrp TO i_planrgrp.
              REFRESH i_planrgrp_up.
              CLEAR wa_planrgrp_up.
              wa_planrgrp_up-orderid     = wa_subscr1-aufnr.
              wa_planrgrp_up-plangroup   = 'X'.
              APPEND wa_planrgrp_up TO i_planrgrp_up.
    *----Change order details with Technician name
              CALL FUNCTION 'BAPI_ALM_ORDER_MAINTAIN'
                TABLES
                  it_methods   = i_methods
                  it_header    = i_planrgrp
                it_header_up = i_planrgrp_up
                  it_partner   = i_partner
                  return       = i_return.
    Thanks & regards,
    Krishna

    Try this way
    CALL FUNCTION 'BAPI_SERVNOT_CREATE'
    EXPORTING
    * EXTERNAL_NUMBER =
    notif_type = 'S3'
    notifheader = ls_notif_h
    * TASK_DETERMINATION = ' '
    * SENDER =
    * ORDERID =
    IMPORTING
    NOTIFHEADER_EXPORT = ls_notif_e
    TABLES
    * NOTITEM =
    * NOTIFCAUS =
    * NOTIFACTV =
    * NOTIFTASK =
    * NOTIFPARTNR =
    * LONGTEXTS =
    * KEY_RELATIONSHIPS =
    return = lt_return
    * IF lt_return IS INITIAL.                                               " <<< Comment this lie
    read table  lt_return into ls_return with key type = 'E'. " << Change
    if sy-subrc ne 0.                                                             " << Change
    COMMIT WORK AND WAIT.
    write: / ls_notif_e-NOTIF_NO.
    ELSE.
    LOOP AT lt_return INTO ls_return.
    WRITE:/ 'errors'.
    * ls_return.
    ENDLOOP.
    endif.

  • User Exit or BADI to update the service order  in R/3

    Hi,
    When creating a service order the following fields need to be populated automatically using an user exit or badi.
    1. Planner Group
    2. PMActType – Plant maintenance activity type
    3. Cost/Profit Centre
    4. WBS element
    5. Work center
    so my requirement is there any function module or Badi or user exit to update the service order details when service order is created / changed.
    Pls do the needful.
    Reg
    Ramana

    Hi Ramana,
    Go to SPRO Transaction and follow the below path
    Customer relationship management>Transactions>Settings for Service Processes>Business Add-Ins and you will find 8 BADI's.
    Check these BADI's useful for you.
    Regards,
    Lijo Joseph

  • I keep getting the following message when trying to update my iPhone: An error occurred while backing up this iPhone (-402636798).

    I keep getting the following message when trying to update my iPhone:  An error occurred while backing up this iPhone (-402636798) Help

    You can not create an iCloud account on a PC, you may create one on an iPad, iPhone or a Mac

  • I updated my ipod touch, then a while later it said waiting for update then shut off. then started turning on and off, what do i do ?

    I updated my ipod touch, then a while later it said waiting for update then shut off. then started turning on and off, what do i do ?

    Try:
    - iOS: Not responding or does not turn on
    - Also try DFU mode after try recovery mode
    How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
    - If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
    - If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
    Apple Retail Store - Genius Bar       

  • Systemd-tmpfiles-setup.service failure

    Good evening friends.
    I recently made a fresh install of arch linux on my pc and since the first boot up i get this error:
    systemd-tmpfiles-setup.service failure
    Failded to start create volatile files and directories
    When i used "systemctl status" command on it, it said something about unkwnon groups in usr/lib/... somewhere, i can't remember all of it, because after i rebooted and tried the same command, it only said that the process failed, without giving much on details.
    What might be the problem here?
    Last edited by NotaName (2014-09-14 17:42:37)

    falconindy wrote:
    Just a guess, but I think you might have some unknown groups in usr/lib/... somewhere.
    You'll really need to try harder to get the logs. They're still in the journal.
    Thanks for the answer.
    Well, i'm still working on the log finding part, as i'm not sure where they are supposed to be. I checked the /var/log folder files, but it seems that they are not readable/binary maybe?
    P.S. Is this something that i might ignore if i don't find a way to fix it?
    Last edited by NotaName (2014-09-14 19:36:47)

  • Invoice not updated for Service and limit items

    Hi All,
    For service and limit we are not able to see the invoice document in the "Related Documents" tab in the Purchase order.
    For material I am able to find the entry in the tab but the invoice statistics data is not getting updated for service POu2019s and also for limit item POu2019s.
    Found a note for the same : 1462644 - Empty statistics in PO in case of Extended Classic Scenario but it works only for material line items only.
    Please let me know if any config change need to be made else if there is any SAP note that would resolve this issue.
    Thanks in advance.
    Regards,
    Catherine

    A knowledge based article note was applied to resolve the issue.
    Regards,
    Catherine

Maybe you are looking for