Systemd pyload.service errors

Hi all,
I moved to systemd successfully and want to use it to start pyload - I followed the wiki page
The service seems to start for less than a minutes and then stop, See below the terminal output of "sudo journalctl -n"
-- Logs begin at Wed, 2012-10-31 14:34:08 GMT, end at Thu, 2012-11-01 10:21:17 GMT. --
Nov 05 11:40:29 linuxbox sudo[3890]: pam_unix(sudo:session): session opened for user root by sweetth(uid=0)
Nov 05 11:40:29 linuxbox sudo[3890]: pam_unix(sudo:session): session closed for user root
Nov 05 11:41:21 linuxbox systemd[1]: pyload.service operation timed out. Terminating.
Nov 05 11:41:21 linuxbox systemd[1]: Failed to start Downloadtool for One-Click-Hoster written in python..
Nov 05 11:41:21 linuxbox systemd[1]: Unit pyload.service entered failed state
Nov 05 11:41:26 linuxbox sudo[3927]: sweetth : TTY=pts/0 ; PWD=/home/sweetth ; USER=root ; COMMAND=/usr/bin/systemctl status pyload.service
Nov 05 11:41:26 linuxbox sudo[3927]: pam_unix(sudo:session): session opened for user root by sweetth(uid=0)
Nov 05 11:41:26 linuxbox sudo[3927]: pam_unix(sudo:session): session closed for user root
Nov 05 11:42:39 linuxbox sudo[3985]: sweetth : TTY=pts/0 ; PWD=/home/sweetth ; USER=root ; COMMAND=/usr/bin/journalctl -n
Nov 05 11:42:39 linuxbox sudo[3985]: pam_unix(sudo:session): session opened for user root by sweetth(uid=0)
And the pyload.service file:
[Unit]
Description=Downloadtool for One-Click-Hoster written in python.
After=network.target
[Service]
Type=forking
PIDFile=/run/pyload/pyload.pid
ExecStart=/usr/bin/pyLoadCore --daemon
KillSignal=SIGQUIT
User=sweetth
[Install]
WantedBy=multi-user.target
Many thanks for your time and assistance,

Hello sweetthdevil,
I had the same problem and I solved it. If you start pyload as a user, you'll find the pyload.pid file in your home folder. So you have to edit the PIDFile entry:
PIDFile=/home/$USER/.pyload/pyload.pid
Regards Moritz

Similar Messages

  • 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.

  • Systemd logind.service reports an error: Failed to start login service

    Hello,
    I found this error in /var/log/errors.log and /var/log/daemon.log although my system functions normally.
    It's been written there every 90 seconds!!!!:
    Dec 19 23:52:59 localhost systemd[1]: Failed to start Login Service.
    Dec 19 23:54:29 localhost systemd[1]: Failed to start Login Service.
    Dec 19 23:55:59 localhost systemd[1]: Failed to start Login Service.
    Dec 19 23:57:29 localhost systemd[1]: Failed to start Login Service.
    Dec 19 23:58:59 localhost systemd[1]: Failed to start Login Service.
    the process: systemd-logind.service seems to be working fine:
    [xxx@archbox ~]$ sudo systemctl status systemd-logind.service
    [sudo] password for xxx:
    systemd-logind.service - Login Service
    Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
    Active: activating (start) since Wed, 2012-12-19 23:49:59 CET; 49s ago
    Docs: man:systemd-logind.service(8)
    man:logind.conf(5)
    http://www.freedesktop.org/wiki/Software/systemd/multiseat
    Main PID: 11822 (systemd-logind)
    CGroup: name=systemd:/system/systemd-logind.service
    └─11822 /usr/lib/systemd/systemd-logind
    Dec 19 23:49:59 archbox systemd[1]: Starting Login Service...
    Dec 19 23:49:59 archbox systemd-logind[11822]: New seat seat0.
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event6 (P...on)
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event7 (V...us)
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event4 (L...ch)
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event5 (S...on)
    Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event3 (T...ns)
    Dec 19 23:49:59 archbox systemd-logind[11822]: New session 1 of user xxx.
    Dec 19 23:49:59 archbox systemd-logind[11822]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-...ay.
    and journalctl _PID=11822 returns:
    Dec 19 23:38:01 archbox sudo[21335]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session closed for user root
    Dec 19 23:38:44 archbox sudo[22682]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session closed for user root
    Dec 19 23:39:10 archbox sudo[23516]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:39:10 archbox sudo[23516]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
    Dec 19 23:39:29 archbox systemd[1]: Failed to start Login Service.
    Dec 19 23:39:29 archbox systemd[1]: Unit systemd-logind.service entered failed state
    Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
    Dec 19 23:39:29 archbox systemd[1]: Stopping Login Service...
    Dec 19 23:39:29 archbox systemd[1]: Starting Login Service...
    Dec 19 23:39:29 archbox systemd-logind[24096]: New seat seat0.
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event6 (Power B
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event7 (Video B
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event4 (Lid Swi
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event5 (Sleep B
    Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event3 (ThinkPa
    Dec 19 23:39:29 archbox systemd-logind[24096]: New session 1 of user xxx.
    Dec 19 23:39:29 archbox systemd-logind[24096]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
    Dec 19 23:39:30 archbox sudo[23516]: pam_unix(sudo:session): session closed for user root
    Dec 19 23:40:08 archbox sudo[25314]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:40:08 archbox sudo[25314]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:40:09 archbox sudo[25314]: pam_unix(sudo:session): session closed for user root
    Dec 19 23:40:43 archbox slim[641]: error 8: BadMatch (invalid parameter attributes) request 142 mino
    Dec 19 23:40:43 archbox slim[641]: error 9: BadDrawable (invalid Pixmap or Window parameter) request
    Dec 19 23:40:43 archbox slim[641]: error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0
    Dec 19 23:40:56 archbox sudo[26739]: xxx : TTY=pts/0 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
    Dec 19 23:40:56 archbox sudo[26739]: pam_unix(sudo:session): session opened for user root by xxx(uid
    Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
    Dec 19 23:40:59 archbox systemd[1]: Failed to start Login Service.
    Dec 19 23:40:59 archbox systemd[1]: Unit systemd-logind.service entered failed state
    Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
    Dec 19 23:40:59 archbox systemd[1]: Stopping Login Service...
    Dec 19 23:40:59 archbox systemd[1]: Starting Login Service...
    Dec 19 23:40:59 archbox systemd-logind[26935]: New seat seat0.
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event6 (Power B
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event7 (Video B
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event4 (Lid Swi
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event5 (Sleep B
    Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event3 (ThinkPa
    Dec 19 23:40:59 archbox systemd-logind[26935]: New session 1 of user xxx.
    Dec 19 23:40:59 archbox systemd-logind[26935]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
    Updating system with pacman didn't solve it.
    Did I miss something out while migrating to systemd, is it a problem with SLiM or user session maybe ? Do you guys have any ideas where to start ? Thanks.
    Last edited by nastycino (2012-12-30 17:46:43)

    My /etc/systemd/logind.conf:
    # This file is part of systemd.
    # systemd is free software; you can redistribute it and/or modify it
    # under the terms of the GNU Lesser General Public License as published by
    # the Free Software Foundation; either version 2.1 of the License, or
    # (at your option) any later version.
    # See logind.conf(5) for details
    [Login]
    #NAutoVTs=6
    #ReserveVT=6
    #KillUserProcesses=no
    #KillOnlyUsers=
    #KillExcludeUsers=root
    #Controllers=
    #ResetControllers=cpu
    #InhibitDelayMaxSec=5
    HandlePowerKey=poweroff
    HandleSuspendKey=suspend
    HandleHibernateKey=hibernate
    HandleLidSwitch=suspend
    #PowerKeyIgnoreInhibited=no
    #SuspendKeyIgnoreInhibited=no
    #HibernateKeyIgnoreInhibited=no
    #LidSwitchIgnoreInhibited=yes
    Is there any way of reinstalling parts of systemd like logind.service?

  • Systemd switchover - pyload.service always fails

    I have finally moved my home server over to systemd (last night) and spent today enabling all relevant daemons and services and rebooting.
    I'm now faced with a number of issues, including a slowdown of the system and SSH login (gone from 1-2 seconds login to ~15 seconds to login)
    I will created separate threads for each issue / service.
    pyload.service always fails to start
    I have re-run the setup using pyLoadCore -s and everything goes smoothly, I am even able to access the web interface. However, when I exit out of terminal the service stops, so I try to load it using systemctl and it does the same as with my httpd.service issue - it begins, works for a few seconds/minute and then fails. During this small timeframe everything works fine before it fails.
    It is beginning to look like there is some issue with systemctl not letting specific services to fully load, or something (I don't know lol)

    kaipee wrote:Because I spent about 10 hours doing a full system switchover and cleaning up the mess including around 20 pacnew files. I thought it would have been easy to ask someone for a bit of help looking at something with a fresh set of eyes what with it being a 'support' forum and all.
    While I can empathize with the ammount of work you may have had to do, this forum is not here for questions users could easily answer on their own except they are just to tired/lazy to do so.  You expect someone else to do the leg work for you when you are unwilling?
    Again, I can empathize with being tired.  But if you are tired, have a beer and a good night's sleep and come back to working on your system with your own fresh set of eyes.  You are right that this can be a support forum - but it is not a servant forum.
    If/when you have done your own work and still face challenges, we are here to help.  But most here also prefer to help by guiding a user in finding their own answers rather than giving them an answer they don't understand - the whole "teach a man to fish..."
    So don't ask for fish-hand-outs.  Come with rod in hand asking where to cast.

  • [Solved] custom systemd service error: Error spawning dbus-launch

    Hello!
    I wroted a shell script to change gnome background
    gsettings set org.gnome.desktop.background picture-uri "/tmp/wallpaper.jpg"
    After that i wrote a systemd wall.service file to launch it
    [Unit]
    Description=Change wallpaper
    After=gdm.service
    [Service]
    Type=oneshot
    ExecStart=test.sh
    [Install]
    WantedBy=graphical.target
    When i try systemctl start wall.service, nothing happens and systemctl status wall.service gives me
    dconf-WARNING **: failed to commit changes to dconf: Error spawning command line 'dbus-launch --autolaunch=74d66c08eacb4e12a2219f3fe74c245b --binary-syntax --close-stderr': Child process exited with code 1
    Where the problem hides?
    Last edited by anptr (2014-06-12 18:08:17)

    tomk wrote:Not a gnome user myself, but if I wanted something to change the wallpaper in my Openbox setup I wouldn't involve systemd at all. I would have thought gnome would have some utility for this built-in, but if not use nitrogen, feh, or other such tools.
    This.
    Really, you are just trying to make things overly complex.  But I was just trying to tell you how to achieve your goal along the path you were taking.  I too wouldn't involve systemd for such a task.  The advantages that systemd provides just aren't necessary for such a process.
    Edit: Besides that, I think you would have to specify the $DISPLAY as well somewhere in that setup.  Either in the service file or the script you wrote.
    Last edited by WonderWoofy (2014-06-08 15:49:01)

  • [Solved] Suspend to Disk: systemd-hibernate.service Fails

    Howdy-ha, folks.  I know this looks pretty mundane, but for the life of me I can't get hibernation to work.  Each time I run systemctl hibernate the screen will go blank as though preparing to suspend, then come back on; journalctl shows the same error messages:
    PM: Cannot find swap device, try swapon -a.
    PM: Cannot get swap writer
    Failed to start Hibernate.
    Dependency failed for Hibernate.
    Service sleep.target is not needed anymore. Stopping.
    Unit systemd-hibernate.service entered failed state.
    This happens when swap is mounted, and "swapon" says as much.  I've been working on this for about four hours now, and none of what I've found seems to pertain to my situation (most of the "solutions" were "Increase partition size').
    What I've tried:
    - Three different kernels---linux-ck custom build and linux-ck-sandybridge from graysky's repo (both with BFQ and CFQ: see below), as well as the stock Arch kernel
    - A 2 Gb swap file at /swapfile on my SSD;
    - A 4 Gb swap partition on /dev/mmcblk0 (an SD card, and my preferred method/location, if possible);
    - An 8 Gb swap partition on HDD /dev/sdb2
    Reasons for wanting hibernate rather than suspend-to-RAM:
    - Maximize battery life.
    - There's some kind of issue with Linux-ck and suspending to RAM; it'll work once, then freeze in a kernel panic the second time, forcing a hard reset.  The stock kernel suspends to RAM, but still won't hibernate
    - I put a lot of time into building a custom Linux-ck kernel, and would rather not have to start the configuration over with the stock kernel if possible.
    I'm working with limited space on my boot drive and, as mentioned, increasing the amount of swap has no bearing on this.  The resulting phenomenon and error messages are the same, regardless of size and medium.  I've exhausted my ideas on where to look, and what to even look for.  Thanks a lot to everyone in advance (especially you,karol; don't think I don't see you lurking back there )
    Last edited by ANOKNUSA (2013-11-17 05:32:14)

    I rebooted, so trying to recreate the same situation:
    $ free -h
    total used free shared buffers cached
    Mem: 7.7G 7.2G 525M 0B 32M 2.3G
    -/+ buffers/cache: 4.8G 2.9G
    Swap: 3.7G 0B 3.7G
    top reports nearly the same thing:
    top - 20:00:13 up 22 min, 1 user, load average: 0.12, 0.22, 0.14
    Tasks: 155 total, 1 running, 154 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 0.1 us, 0.3 sy, 0.1 ni, 99.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
    KiB Mem: 8061380 total, 7500096 used, 561284 free, 34432 buffers
    KiB Swap: 3872236 total, 0 used, 3872236 free, 2417172 cached
    htop, however, reports about 1.5 Gb more free RAM.  After reboot, swappiness is still set to 100 with the same results.
    EDIT:
    ANOKNUSA wrote: I'll test it again with the other locations mentioned in the OP, and get back to you.
    Even though I rebooted, I haven't done this yet, so ignore it for the moment.
    Last edited by ANOKNUSA (2013-08-28 01:06:10)

  • [SOLVED] Getting my systemd user service to talk to dbus

    I'm currently trying to set up a nice email workflow with mbsync, msmtp and notmuch.
    My passwords are saved in the Gnome keyring "login", and I've configured mbsync to use secret-tool to retrieve them. Unfortunately when secret-tool is invoked from this systemd user service there is an error when it in turn tries to call dbus-launch.
    Here is the error:
    $ systemctl --user status -l mbsync.service
    ● mbsync.service - Synchronise IMAP folders
    Loaded: loaded (/home/leo/.config/systemd/user/mbsync.service; static; vendor preset: enabled)
    Active: failed (Result: exit-code) since Sun 2015-05-10 20:10:56 BST; 17min ago
    Process: 3691 ExecStart=/usr/bin/mbsync -a (code=exited, status=1/FAILURE)
    Main PID: 3691 (code=exited, status=1/FAILURE)
    May 10 20:10:55 think3 mbsync[3691]: (secret-tool:3696): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
    May 10 20:10:55 think3 mbsync[3691]: secret-tool: Error spawning command line 'dbus-launch --autolaunch=388eb9d3cc5542d5922d60c8f9605b31 --binary-syntax --close-stderr': Child process exited with code 1
    May 10 20:10:55 think3 mbsync[3691]: Skipping account ymail, password command exited with status 1
    May 10 20:10:56 think3 mbsync[3691]: (secret-tool:3698): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
    May 10 20:10:56 think3 mbsync[3691]: secret-tool: Error spawning command line 'dbus-launch --autolaunch=388eb9d3cc5542d5922d60c8f9605b31 --binary-syntax --close-stderr': Child process exited with code 1
    May 10 20:10:56 think3 mbsync[3691]: Skipping account gmail, password command exited with status 1
    May 10 20:10:56 think3 systemd[716]: mbsync.service: main process exited, code=exited, status=1/FAILURE
    May 10 20:10:56 think3 systemd[716]: Failed to start Synchronise IMAP folders.
    May 10 20:10:56 think3 systemd[716]: Unit mbsync.service entered failed state.
    May 10 20:10:56 think3 systemd[716]: mbsync.service failed.
    The file mbsync.service is simply
    [Unit]
    Description=Synchronise IMAP folders
    Wants=network-online.target
    After=network-online.target
    [Service]
    Type=oneshot
    ExecStart=/usr/bin/mbsync -a
    Any ideas how I can use secret-tool from within a systemd user service? The Wiki includes some information about DBus and systemd here but it looks a little outdated...
    Last edited by curiousleo (2015-05-22 22:02:33)

    barbae wrote:Please could you post the output of 'journalctl -b' just after user login into gnome through gdm?
    Sure thing. Here it is (I've cut out some stuff that obviously had nothing to do with the problem at hand):
    May 17 17:17:11 think3 systemd[1]: systemd 219 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
    May 17 17:17:11 think3 systemd[1]: Created slice Root Slice.
    May 17 17:17:11 think3 systemd[1]: Starting Root Slice.
    May 17 17:17:11 think3 systemd[1]: Created slice System Slice.
    May 17 17:17:11 think3 systemd[1]: Starting System Slice.
    May 17 17:17:11 think3 systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    May 17 17:17:11 think3 systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    May 17 17:17:11 think3 systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    May 17 17:17:11 think3 systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    May 17 17:17:11 think3 systemd[1]: Reached target Login Prompts.
    May 17 17:17:11 think3 systemd[1]: Starting Login Prompts.
    May 17 17:17:11 think3 systemd[1]: Created slice User and Session Slice.
    May 17 17:17:11 think3 systemd[1]: Starting User and Session Slice.
    May 17 17:17:11 think3 systemd[1]: Reached target Slices.
    May 17 17:17:11 think3 systemd[1]: Starting Slices.
    May 17 17:17:11 think3 systemd[1]: Started Create System Users.
    May 17 17:17:11 think3 systemd[1]: Created slice system-systemd\x2drfkill.slice.
    May 17 17:17:11 think3 systemd[1]: Starting system-systemd\x2drfkill.slice.
    May 17 17:17:11 think3 systemd[1]: Started Commit a transient machine-id on disk.
    May 17 17:17:11 think3 systemd[1]: Started Daily verification of password and group files.
    May 17 17:17:11 think3 systemd[1]: Starting Daily verification of password and group files.
    May 17 17:17:11 think3 systemd[1]: Listening on D-Bus System Message Bus Socket.
    May 17 17:17:11 think3 systemd[1]: Starting D-Bus System Message Bus Socket.
    May 17 17:17:11 think3 systemd[1]: Reached target Sockets.
    May 17 17:17:11 think3 systemd[1]: Starting Sockets.
    May 17 17:17:11 think3 systemd[1]: Reached target Basic System.
    May 17 17:17:11 think3 systemd[1]: Starting Basic System.
    May 17 17:17:11 think3 systemd[1]: Starting Login Service...
    May 17 17:17:11 think3 systemd[1]: Starting Permit User Sessions...
    May 17 17:17:11 think3 systemd[1]: Started D-Bus System Message Bus.
    May 17 17:17:11 think3 systemd[1]: Starting D-Bus System Message Bus...
    May 17 17:17:11 think3 systemd[1]: Reached target Timers.
    May 17 17:17:11 think3 systemd[1]: Starting Timers.
    May 17 17:17:11 think3 systemd[1]: Started Permit User Sessions.
    May 17 17:17:11 think3 systemd[1]: Starting GNOME Display Manager...
    May 17 17:17:11 think3 systemd[1]: Started Login Service.
    May 17 17:17:12 think3 systemd[1]: Started GNOME Display Manager.
    May 17 17:17:12 think3 systemd[1]: Reached target Multi-User System.
    May 17 17:17:12 think3 systemd[1]: Starting Multi-User System.
    May 17 17:17:12 think3 systemd[1]: Reached target Graphical Interface.
    May 17 17:17:12 think3 systemd[1]: Starting Graphical Interface.
    May 17 17:17:12 think3 systemd-logind[293]: New seat seat0.
    May 17 17:17:12 think3 dbus[301]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
    May 17 17:17:12 think3 systemd[1]: Reached target User and Group Name Lookups.
    May 17 17:17:12 think3 systemd[1]: Starting User and Group Name Lookups.
    May 17 17:17:12 think3 systemd[1]: Starting Accounts Service...
    May 17 17:17:13 think3 dbus[301]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
    May 17 17:17:13 think3 systemd[1]: Starting Authorization Manager...
    May 17 17:17:13 think3 polkitd[443]: Started polkitd version 0.112
    May 17 17:17:13 think3 polkitd[443]: Loading rules from directory /etc/polkit-1/rules.d
    May 17 17:17:13 think3 polkitd[443]: Loading rules from directory /usr/share/polkit-1/rules.d
    May 17 17:17:13 think3 polkitd[443]: Finished loading, compiling and executing 3 rules
    May 17 17:17:13 think3 dbus[301]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    May 17 17:17:13 think3 polkitd[443]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
    May 17 17:17:13 think3 systemd[1]: Started Authorization Manager.
    May 17 17:17:13 think3 accounts-daemon[436]: started daemon version 0.6.40
    May 17 17:17:13 think3 dbus[301]: [system] Successfully activated service 'org.freedesktop.Accounts'
    May 17 17:17:13 think3 systemd[1]: Started Accounts Service.
    May 17 17:17:13 think3 systemd[1]: Created slice user-120.slice.
    May 17 17:17:13 think3 systemd[1]: Starting user-120.slice.
    May 17 17:17:13 think3 systemd[1]: Starting User Manager for UID 120...
    May 17 17:17:13 think3 systemd-logind[293]: New session c1 of user gdm.
    May 17 17:17:13 think3 systemd[1]: Started Session c1 of user gdm.
    May 17 17:17:13 think3 systemd[1]: Starting Session c1 of user gdm.
    May 17 17:17:13 think3 systemd[454]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
    May 17 17:17:13 think3 systemd[454]: Unit type .busname is not supported on this system.
    May 17 17:17:13 think3 systemd[454]: Reached target Paths.
    May 17 17:17:13 think3 systemd[454]: Starting Paths.
    May 17 17:17:13 think3 systemd[454]: Reached target Timers.
    May 17 17:17:13 think3 systemd[454]: Starting Timers.
    May 17 17:17:13 think3 systemd[454]: Reached target Sockets.
    May 17 17:17:13 think3 systemd[454]: Starting Sockets.
    May 17 17:17:13 think3 systemd[454]: Reached target Basic System.
    May 17 17:17:13 think3 systemd[454]: Starting Basic System.
    May 17 17:17:13 think3 systemd[454]: Reached target Default.
    May 17 17:17:13 think3 systemd[454]: Startup finished in 3ms.
    May 17 17:17:13 think3 systemd[454]: Starting Default.
    May 17 17:17:13 think3 systemd[1]: Started User Manager for UID 120.
    May 17 17:17:13 think3 gnome-session[460]: glamor: EGL version 1.4 (DRI2):
    May 17 17:17:13 think3 org.a11y.Bus[459]: Activating service name='org.a11y.atspi.Registry'
    May 17 17:17:13 think3 org.a11y.Bus[459]: Successfully activated service 'org.a11y.atspi.Registry'
    May 17 17:17:13 think3 org.a11y.atspi.Registry[518]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    May 17 17:17:14 think3 polkitd[443]: Registered Authentication Agent for unix-session:c1 (system bus name :1.9 [gnome-shell --mode=gdm --wayland --display-server], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8)
    May 17 17:17:18 think3 gdm-password][674]: pam_unix(gdm-password:session): session opened for user leo by (uid=0)
    May 17 17:17:18 think3 systemd[1]: Created slice user-1000.slice.
    May 17 17:17:18 think3 systemd[1]: Starting user-1000.slice.
    May 17 17:17:18 think3 systemd[1]: Starting User Manager for UID 1000...
    May 17 17:17:18 think3 systemd[1]: Started Session c2 of user leo.
    May 17 17:17:18 think3 systemd-logind[293]: New session c2 of user leo.
    May 17 17:17:18 think3 systemd[1]: Starting Session c2 of user leo.
    May 17 17:17:18 think3 systemd[717]: pam_unix(systemd-user:session): session opened for user leo by (uid=0)
    May 17 17:17:18 think3 systemd[717]: Unit type .busname is not supported on this system.
    May 17 17:17:18 think3 systemd[717]: Started Synchronise e-mails and create database dump once a day.
    May 17 17:17:18 think3 systemd[717]: Starting Synchronise e-mails and create database dump once a day.
    May 17 17:17:18 think3 systemd[717]: Reached target default.target.
    May 17 17:17:18 think3 systemd[717]: Startup finished in 13ms.
    May 17 17:17:18 think3 systemd[717]: Starting default.target.
    May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: /etc/gdm/Xsession: Beginning session setup...
    May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: localuser:leo being added to access control list
    May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
    May 17 17:17:18 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.a11y.Bus'
    May 17 17:17:19 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.a11y.Bus'
    May 17 17:17:19 think3 org.a11y.Bus[732]: Activating service name='org.a11y.atspi.Registry'
    May 17 17:17:19 think3 org.a11y.Bus[732]: Successfully activated service 'org.a11y.atspi.Registry'
    May 17 17:17:19 think3 org.a11y.atspi.Registry[756]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
    May 17 17:17:19 think3 gnome-session[734]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
    May 17 17:17:19 think3 gnome-session[734]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
    May 17 17:17:19 think3 gnome-session[734]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
    May 17 17:17:20 think3 polkitd[443]: Registered Authentication Agent for unix-session:c2 (system bus name :1.43 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.utf8)
    May 17 17:17:20 think3 gnome-session[734]: Entering running state
    May 17 17:17:21 think3 gnome-shell[804]: GNOME Shell started at Sun May 17 2015 17:17:20 GMT+0100 (BST)
    May 17 17:17:52 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.gnome.seahorse.Application'
    May 17 17:17:52 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.gnome.seahorse.Application'
    May 17 17:20:48 think3 /usr/lib/gdm/gdm-x-session[725]: Activating service name='org.gnome.seahorse.Application'
    May 17 17:20:48 think3 /usr/lib/gdm/gdm-x-session[725]: Successfully activated service 'org.gnome.seahorse.Application'

  • [SOLVED] Borked systemd setup -- dbus errors during boot; can't login

    I have error messages very similar to this post. Unfortunately, as the author states, he never persisted in solving it but instead re-installed from scratch. I'd rather not do that.
    For reference, I have a pure systemd setup -- no rc.conf file, no initscripts package, etc.
    At boot I get the "Welcome to Arch!" messages followed by the various [OK] lines and then I get blindingly fast repeating lines about dbus not starting and attempting to restart it too quickly. If I walk away for about 1-2min, I finally see a login screen, but after entering my username/password, it just sits there and does nothing.
    As for suspects... I had systemd working fine.
    -- I updated some packages (not more than a few days worth and I'd have to check the list)
    -- I also took care of manual updates to some .pacnew files I periodically check for. In this group were some biggies: group, shadow, and passwd. I did recall the odd bit about uuidd changing from uid 995 to 68, but in reading about that since then, it doesn't seem to be a big deal.
    I've been booting in by appending
    systemd.unit=emergency.target
    to the kernel line, but my exploration hasn't been all that helpful. `journalctl since=date` reveals the errors, but I don't get much information about why dbus is having issues starting.
    emergency.target also doesn't seem to be that helpful since I can't do anything with a read-only system. I'd love some suggestions about what, specifically, to check for before I reboot from Windows back into Arch and record more careful notes, probably by jotting notes onto a flash drive. Any places to start? For reference, I've done:
    -- systemctl status dbus: lists as inactive (dead) and simply shows the errors I see at boot (failed to start)
    -- systemctl list-units
    -- systemctl list-unit-files
    -- journalctl and looking around for instances of fail or failed or dbus
    If I start systemd-logind.service or dbus.service, it displays a status message about running fsck and then takes me to a login prompt automatically. Then I can type in my username and password and then there's nothing after that. No prompt, just an apparent hang.
    Thanks for any suggestions -- I'll take them and then collect more detailed results and report back.
    Thanks!
    Last edited by jwhendy (2012-11-08 16:07:33)

    As I wondered, I think it's a problem with passwd. I don't have a dbus entry and must have missed it when I was copying things around between my version and the .pacnew. Downloading an install disc now since I can't seem to change it from the recovery console due to mounting root read-only.
    I'd love to know of a way to boot that avoids starting dbus and other things that might break while still having read/write access to root. Will mark solved once I update /etc/passwd and reboot.

  • [SOLVED] Trouble with running systemd user service on login

    I'm trying to get emacs to run as a systemd/user service so that it will start up faster, as suggested in the wiki article, but I'm having some problems.
    I can't get the service to run as soon as I log in. I can run the service with
    systemctl --user start emacs
    and it will run for the rest of my session, but if I try to run
    systemctl --user enable emacs
    I get the following error:
    The unit files have no [Install] section. They are not meant to be enabled
    using systemctl.
    Possible reasons for having this kind of units are:
    1) A unit may be statically enabled by being symlinked from another unit's
    .wants/ or .requires/ directory.
    2) A unit's purpose may be to act as a helper for some other unit which has
    a requirement dependency on it.
    3) A unit may be started when needed via activation (socket, path, timer,
    D-Bus, udev, scripted systemctl call, ...).
    I ran
    systemctl --user is-enabled emacs
    and that returned
    static
    but I'm not sure what that means. Any help would be greatly appreciated.
    Last edited by whitebrice (2014-06-28 17:20:13)

    Are you sure there isn't a typo in your unit file? The example you linked to in the wiki does have an [Install] section.
    Post your ~/.config/systemd/user/emacs.service file here so we can take a look.

  • SharePoint Foundation 2010: search error: "Your search cannot be completed because of a service error."

    Hi,
    I have SharePoint Foundation 2010 running on a single server with databases, with a second server in the farm serving as a 2nd app tier. Both server have the exact same versions of SharePoint loaded (according to the Central Admin site).
    Whenever I try to run a search from any site in my SharePoint Foundation 2010 installation (in this example I typed "this is my query"), it hangs for 20-30 seconds while the IE status bar says:
    Waiting for http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2Ftfs2010db%2Ftfs%2FSITE1
    Then it finally returns a results screen with an error that says: "Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information."
    Checking the SharePoint logs under C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS, the relevant entries say the following (items I deem important
    bolded):
     11/05/2011 18:22:25.88 w3wp.exe (0x35F0) 0x1908 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (HEAD:http://172.22.100.101:80/)) 11/05/2011 18:22:25.88 w3wp.exe (0x35F0) 0x1908 SharePoint Foundation Logging
    Correlation Data xmnv Medium Name=Request (HEAD:http://172.22.100.101:80/) a7ab70a3-61bd-4d62-b5a4-cf77a45dafb9
    11/05/2011 18:22:25.88 w3wp.exe (0x35F0) 0x1908 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (HEAD:http://172.22.100.101:80/)). Execution Time=3.33645756653429 a7ab70a3-61bd-4d62-b5a4-cf77a45dafb9
    11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1))
    11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1)
    fea6cc87-0404-497a-838e-5e154f422aa4
    11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1)).
    Execution Time=4.3055751499143 fea6cc87-0404-497a-838e-5e154f422aa4
    11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1))
    11/05/2011 18:22:50.73 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1)
    5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:22:50.75 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Logging Correlation Data xmnv Medium Site=/tfs/SITE1 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:22:50.77 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Search Query dn6r High FetchDataFromURL start at(outside if): 1 param: start 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:22:50.79 mssearch.exe (0x58A4) 0x2534 SharePoint Foundation Search QueryComponentSelection aee7 Medium
    Did You Mean Suggester not found. [smart2.hxx:382] d:\office\source\otools\inc\search\common\ytrip\tripoli\smart2.hxx 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:22:50.91 mssearch.exe (0x58A4) 0x2534 SharePoint Foundation Search Query Processor e0pg Medium 1dd958fb-b605-4b3b-a676-28a3cafb2eb6:
    Query completed 125 ms, detailed time: Query stage execution ms times: 0 125 0 0 125 0 0 0 Query stage cpu ms times: 0 31 0 0 31 0 0 0 Query stage hit counts: 1 1 1 7 1 0 1 1 Cursor count: 260 Mapped page count: 164 Total index count: 7 [srequest.cxx:5526]
    d:\office\source\search\native\ytrip\tripoli\cifrmwrk\srequest.cxx 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Search Exceptions 1hjo
    Medium Exception thrown: 0x80040e31 (d:\office\source\otools\inc\search\common\ytrip\tripoli\timeout.hxx:51 ip 0x000007FEECF099B7) 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Search
    Query Processor e2o1 High In CRootQuerySpec::Execute - caught exception: 0x80040e31, translated to: 0x80040e31 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Search Administration 0000
    High Log Query: More Information: Execution stopped because a resource limit was reached. No results were returned.
    5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Web Parts 89a1
    High Error while executing web part: Microsoft.SharePoint.Search.WebControls.Srhdc GenericException: Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.
    ---> System.ServiceProcess.TimeoutException: System error. at Microsoft.SharePoint.Search.Query.KeywordQueryInternal.Execute() at Microsoft.SharePoint.Search.Query.QueryInternal.Execute(QueryProperties properties) at Microsoft.SharePoint.Search.Query.Query.Execute()
    at Microsoft.SharePoint.Search.WebControls.SearchResultHiddenObject.GetResultData() --- End of inner exception stack trace --- at Microsoft.SharePoint.Search.WebControls.SearchResultHiddenObject.get_ResultsReturned() at Microsoft.SharePoint.Search.Internal.WebControls.CoreRes...
    5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:23:06.08* w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Web Parts 89a1 High ...ultsWebPart.ModifyXsltArgumentList(ArgumentClassWrapper argList) at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform(Boolean
    bDeferExecuteTransform) 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Web Parts 89a2
    High InnerException 1: System.ServiceProcess.TimeoutException: System error. at Microsoft.SharePoint.Search.Query.KeywordQueryInternal.Execute() at Microsoft.SharePoint.Search.Query.QueryInternal.Execute(QueryProperties properties) at Microsoft.SharePoint.Search.Query.Query.Execute()
    at Microsoft.SharePoint.Search.WebControls.SearchResultHiddenObject.GetResultData() 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:23:06.08 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (DataBinding DataFormWebPart ()). Execution Time=15302.2074034549 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:23:06.09 w3wp.exe (0x35F0) 0x3148 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://SERVER2010:80/tfs/SITE1/_layouts/searchresults.aspx?k=this%20is%20my%20query&u=http%3A%2F%2FSERVER2010%2Ftfs%2FSITE1)).
    Execution Time=15358.1002613461 5e283c89-990f-4572-ae77-a1e6a5aad502
    11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x58E0 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Request (GET:http://SERVER2010:80/tfs/SITE1/Shared%20Documents/SITE1_logo_sharepoint.png))
    11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x58E0 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://SERVER2010:80/tfs/SITE1/Shared%20Documents/SITE1_logo_sharepoint.png) f0d03f8e-d78b-4004-9a5f-3ee9955afa60
    11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x5C6C SharePoint Foundation General af71 Medium HTTP Request method: GET f0d03f8e-d78b-4004-9a5f-3ee9955afa60
    11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x5C6C SharePoint Foundation General af75 Medium Overridden HTTP request method: GET f0d03f8e-d78b-4004-9a5f-3ee9955afa60
    11/05/2011 18:23:06.59 w3wp.exe (0x35F0) 0x5C6C SharePoint Foundation General af74 Medium HTTP request URL: /tfs/SITE1/Shared%20Documents/SITE1_logo_sharepoint.png f0d03f8e-d78b-4004-9a5f-3ee9955afa60
    11/05/2011 18:23:06.60 w3wp.exe (0x35F0) 0x58E0 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://SERVER2010:80/tfs/SITE1/Shared%20Documents/SITE1_logo_sharepoint.png)). Execution Time=9.75459171486879 f0d03f8e-d78b-4004-9a5f-3ee9955afa60
    Not sure what "resource limit is reached" actually means. This SharePoint installation is running under regular SQL 2008 R2, and the
    WSS_Content database is fairly small (10gig). I've reviewed the Search Service, the process account running it, the
    WSS_SEARCH index database, and verified that the Content database is using the proper index database. Everything looks like it should be crawling/indexing/working fine. But the WSS_SEARCH
    database isn't very large, so I'm not sure if the crawling is actually filling it with anything.
    Not sure where to start seriously troubleshooting this. Any advice would be appreciated. Thanks.

    Hi,
    The query ran in tens of seconds. This indicates that at some point a bad plan compiled and stayed in the cache. 
    It may have gotten there because the statistics were out of date. 
    A possible way to keep this from happening is to rebuild statistics with full scan more frequently.
    Try free the proc cache and see the result.
    http://msdn.microsoft.com/en-us/library/ms174283(v=SQL.105).aspx
    Thanks,
    Rock Wang
    Regards, Rock Wang Microsoft Online Community Support

  • IPod Service Error with iPod installer 2006-06-28

    I previously had a Mini but lost it (stolen). I bought a Nano to replace it but could never get it to work. I returned this and purchased a new 30g iPod. Same issues. I get the error message "iPod Service Error" when I open the 2006-06-28 iPod Software Updater. I even get this message whether I have my iPod connected or not. In iTunes, I get the message "The software required for communicating with the iPod is not installed correctly. Please reinstall iTunes to install the iPod's software."
    Well, I've reinstalled iTunes countless times and reinstalled the updater a equal number of times with no luck. I tried all the steps (including links) in:
    http://docs.info.apple.com/article.html?artnum=93716
    I also used msconfig with no luck. I disabled my Norton internet security and antivirus software with no success. I disabled the Fast User Switching and followed someone's advice regarding FAT32, but again no luck.
    I tried to read through all the latest discussions and articles I could find, but am now getting confused. Is there anyone out there who has been able to tackle this problem? My alternative is returning my iPod and giving up on iTunes. Help me please!! Thanks.
    Dell 8100   Windows XP  
    Dell 8100   Windows XP  

    Thanks for your response and sorry for the delay. I've been traveling. Yes, I did try making another XP user account and got the same results. I have not tried the installer cleanup. What do I do with this utility? I read the instructions from MS, but not sure if I should just highlight the iTunes, iPod, and QuickTime stuff on my PC. Any help would be appreciated.
    Thanks,

  • Reporting Services Error after Interactive sorting and drill down in pps

    Hi 
    i have a report  that has a drill down option that shows all workgroups within a specific  parent group and an interactive sorting ass well on both columns  parent group &  workgroup 
    This is displayed  in pps combined with a SharePoint
    ---the problem is that after sorting the parent group column by name   i then press the drill through icon  (+) next to it hopping to see all workgroups related to each parent group
      - but instead 
    i receive this Reporting Services Error  :
    The value for parameter 'SortItem' is not specified. It is either missing from the function call, or it is set to null. (rsMissingParameter) Get
    Online Help       
    If I don't press the sorting and just drill through it works fine. the sorting itself also works fine. 
    any suggestions ?
     

    Hi Hyaron,
    I am unable to reproduce the issue in my test environment. How did you add the drilldown feature? Were you doing that by setting visibility of the column or of the group? Please ensure to add the drilldown functionality by set the visibility of the workgroup
    from the Grouping Pane in the Report Designer.
    How did you add the Interactive Sorting on the headers of the two columns? Based on the drilldown functionality, the Interactive Sorting on the second column doesn’t work. So, you can move the Interactive Sorting on the second column. When configuring the
    Interactive sorting on the first column, you should set the parent group to sort, and sort by the field that the parent group groups by.
    Hope this helps.
    Regards,
    Mike Yin
    TechNet Community Support

  • Error when starting Netscape Calendar Server: Module: , Label: 355, Service error: #0x13209

    When starting Netscape Calendar Server, the following error message appears:
    <BR><P>
    Module: , Label: 355, Service error: #0x13209
    <P>
    The three ACIs listed below need to be present in the Directory Server in order
    for Calendar server to work properly. Check the properties on the Base DN to
    verify that the following ACIs exist. If they are not present, you will need
    to add them, and the Base DN will need to be modified for your enviroment.
    <P>
    <OL>
    <LI>ACI for allowing users to modify their own entries.<BR>
    <P>
    (targetattr = "*")(version 3.0; acl "Allow self entry modification";
    allow (write)userdn = "ldap:///self";)<BR>
    <P>
    <LI>ACI for allowing anyone permissions to Read, Search, and Compare.<BR>
    <P>
    (target="ldap:///o=basedn.com") (targetattr != "userPassword") (version
    3.0; acl "Anonymous access";
    allow (read, search, compare) userdn = "ldap:///anyone";)<BR>
    <P>
    <LI>ACI for allowing Calendar Server admins Write access to the Base DN
    (this is necessary in order for admins to add users and resources to the node).
    <BR><P>
    (target="ldap:///o=basedn.com") (targetattr = "*") (version 3.0; acl
    "Calendar Administrators Group";<BR>
    allow(all) groupdn = "ldap:///cn=Calendar Server Admins,ou=Netscape
    Servers,o=basedn.com";)<BR>
    </OL>

    Hi Trinidad,
    Thanks for your help!!!
    1.
    I didn't install EventSender and DIProxy yet, I tried first to upload and deploy the zip files, but I couldn't open the Itegration Application Explorer.
    2.
    The jvm.dll file is in in the folder pointed by the logs: C:\Program Files (x86)\SAP\SAP Business One Integration\jdk1.5.0_xx_sap\jre\bin\server
    and it is also in C:\Program Files (x86)\SAP\SAP Business One Integration\jdk1.5.0_xx_sap_64\jre\bin\server
    I tried running the file  java5w.exe, but I got an error message:
    Access is denied
    Unable to open the service tomcat5
    Thne I managed to open it by "rua as administrator".
    the Java Virtual Machine path is points to the java 1.5 version folder.
    Is it possible that the reason that the service can't start is related to administrator rigts??
    In the properties in the Integration Service (services.msc):
    It is set to be run with the local system account.
    all other properties looks fine.
    in the properties of the tomcat5.exe (and tomcat5w.exe  , I tried both)
    In the Compatibility tab I tried setting the flag "Run this program in compatibility mode for" to Vista, windows 7, and server 2008
    I didn't have the option of Windows XP.
    I have also set the Privilege level of: "Run this program as administrator" to true.
    But still the service won't start.
    What can be the problem?
    What else can I check?
    Thanks a lot,
    Chana

  • How to take control back from service error handler in osb

    I am using osb to send data to multiple services at the same time.since x query is a procedural language if any single operation fails the flow goes to service error handler which calls a BPEL webservice and logs the error in a database but the control doesnt comes back to my code I have tried everything including RESUME,REPLY operations but all in vain similarly i cannot use service callout call to my business service because its not allowing to select my BPEL wsdl operation

    If your statement "the control doesnt comes back to my code" means you expect that your xquery will continue in processing than your expectations are just too high. :-)
    Resume action is supposed to resume the next action in the message flow. It means the action that follows the action which caused an error.

  • Won't show up on itunes or on ipod updater("ipod service error")

    Every time i plug my ipod (4g w/ click wheel) it says on itunes software not installed correctly, it shows up as a drive but i can't see it on itunes, i have tried to reinstall itunes more than 5 times and nothing works. Also, when I try to restore my ipod with ipod updater i get an "ipod service error". I am going crazy here trying to figure this out, someone please help me!

    Try this for can't mount iPod:
    http://docs.info.apple.com/article.html?artnum=302538
    You might also want to try putting your iPod in disk mode:
    http://docs.info.apple.com/article.html?artnum=93651
    Sometimes this does the trick (iPod normally needs to be in disk mode in order for it to show up in Disk Management)
    http://docs.info.apple.com/article.html?artnum=93499
    If you're still unable to get your iPod to restore, you can try this:
    Put the iPod into disk mode, according to the article above.
    Connect it to your computer.
    Click Start > Run
    Type compmgmt.msc
    Click on Disk Management (in the left-hand column)
    Let the computer go through its connection process
    Right click on the iPod and click Format
    Set the format to FAT32
    Leave all the other settings on their defaults
    Do Not select the option to Quickformat
    Start the format.
    It's recommended that you still try to restore the iPod after formatting, but it's not always necessary. This should get your iPod back into iTunes.
    CG

Maybe you are looking for

  • The ODS activation is taking long time

    Hi, We are on SAP NetWeaver BI 701 (Support Package 5). We create a Z ODS, it will contain a lot of data (180.000.000 month-end) and we want to generate specific reports about it. The activation is taking long time, I assume is because we checked the

  • Reg File- Webservice Async-Sync bridge

    Hi, I have File -WS async-Sync scenario. I have configured the RequestResponseBean-CallSAP-ResponseOnewayBean in my sender CC When i execute the scenario, the sender channel is throwing Error: java.lang.NullPointerException When i check the sender ch

  • Address Book Images Gone Funky

    Adding images to Address Book contacts just results in a random part of the image showing. In iOS I can add images just fine, and they show up in Address Book ok. It's never done this before. Any ideas??

  • TS1741 How do I turn off my Apple TV?

    How do I turn off my Apple TV?

  • Links to internal functions

    The following tutorial works fine for static html that is hard coded into the tag http://www.xllusion.net/ed/2010/04/26/flex-4-richeditabletexttlf-link-example/comment-page -1/#comment-2057 but I need my text to be bindable and dynamic loading someti