[SOLVED]systemd-fstab-generator and syslog error?

here is the bootup error message:
Nov  2 07:27:58 localhost [    9.207762] systemd-fstab-generator[151]: Failed to create unit file: File exists
Nov  2 07:27:58 localhost [   10.119699] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
Nov  2 07:27:58 localhost [   10.544789] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov  2 07:27:58 localhost [   10.544974] systemd[1]: Failed to listen on Syslog Socket.
and my fstab is here:
# /etc/fstab: static file system information
# <file system>    <dir>    <type>    <options>    <dump>    <pass>
tmpfs        /tmp    tmpfs    nodev,nosuid    0    0
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb5 / jfs defaults 0 1
/dev/sdb6 /home ext4 defaults,user_xattr 0 1
/dev/sdb7 /var reiserfs defaults 0 1
/dev/sdb8 /tmp reiserfs defaults 0 1
Last edited by frat (2012-11-02 03:21:07)

systemd-fstab-generator is fixed,thank you.
syslog errors still:
Nov  2 10:29:44 localhost [   10.051816] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov  2 10:29:44 localhost [   10.052000] systemd[1]: Failed to listen on Syslog Socket.
#systemctl status syslog
syslog.service
      Loaded: error (Reason: No such file or directory)
      Active: inactive (dead)
#systemctl status syslog.socket
syslog.socket - Syslog Socket
      Loaded: loaded (/usr/lib/systemd/system/syslog.socket; static)
      Active: inactive (dead)
        Docs: man:systemd.special(7)
              http://www.freedesktop.org/wiki/Software/systemd/syslog
      CGroup: name=systemd:/system/syslog.socket
any advice?
Last edited by frat (2012-11-02 02:56:37)

Similar Messages

  • [SOLVED] Systemd-fstab-generator: Out of memory...

    Hello using multilib lib32-systemd 208-1 and systemd208-1...  I have a problem where I will boot and it hangs at mounting drives:
    systemd-fstab-generator[135]: Out of Memory.
    systemd[1]:  /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1. 
    I have chrooted in and upgrade stuff and modified my fstab and grub config stuff a bit since I was getting the /root read only problem..  (changed to rw) and it works... However I cannot seem to find where this problem is coming from and the only thing that I can think is that systemd cannot parse /etc/fstab correctly..  My fstab has labels like:  Label=/home, Label=/, Label=/var, Label=/boot, etc...  it was fine till a couple days ago...  Using kernel 3.11.3 x86_64...
    Last edited by adramalech (2013-10-06 20:50:20)

    Okay so here is my fstab:
    tmpfs /dev/shm tmpfs defaults,noatime 0 0
    none /tmp tmpfs defaults,noatimenodev,nosuid,mode=1777 0 0
    /dev/sdd2 none swap sw 0 0
    proc /proc proc nodev,noexec,nosuid 0 0
    # /dev/sdc2 UUID=0cf15f7d-a6e0-4b4b-8ca0-e3fa32ca79f5
    LABEL=/ / ext4 errors=remount-ro,defaults,rw,discard,noatime,data=ordered 0 1
    # /dev/sdc1 UUID=22cee2cf-55fa-4721-b3da-68191c477643
    LABEL=/boot /boot ext2 defaults 0 0
    # /dev/sdc3 UUID=79bcca95-af9a-4f9f-99ab-78020a3960da
    LABEL=/home /home ext4 errors=remount-ro,defaults,rw,noatime,discard,data=ordered 0 1
    /dev/sdd3 /var ext4 errors=remount-ro,defaults,rw,relatime,data=ordered 0 2
    LABEL=Storage /media/Storage ext4 errors=remount-ro,defaults,rw,relatime,data=ordered 0 2
    ***EDIT#1***
    Storage is a WD 2TB Caviar green, same with /var and swap,  /boot, /home, / are on an M4 128GB SSD, and the rest are just stuff put in tmpfs and proc like normal...  Tried keeping the heavily read/write data off of the ssd to conservative with writes
    I am wondering if I can not just update my damn Labels in fstab and through gparted and call it a day...
    ***EDIT#2***
    Okay so I only went through and thought to update packages that needed updating since that might have fixed the problem... I saw an update for lib32-systemd 208-1 and some other non-essentials stuff so updated rebooted and still same problem     I have used this fstab for a considerable amount of years using arch and then back using gentoo for a couple years with no problems... Wondering if now it is being picky with labels...
    Last edited by adramalech (2013-10-06 19:19:49)

  • [Solved] Systemd user service and timer dbus error

    I have installed arch recently and added a few of my own services, for example the acpi_call commands and such. Now I want to create a systemd service that runs every 5 minutes and execute a script.
    I searched a lot and I found that I must use timers. I got the thing with the timers working, but because my script has to do with a specific user, I want it to run only every 5 minutes when i am logged in as that user.
    I tried to put the files in /etc/systemd/users, .config/local/users and all the possibilities but everytime i want to enable it, it says dbus connection refused.
    Can somebody please provide me a way to execute a systemd service every 5 minutes while I am logged in as a specific user?
    I did follow the wiki and created a dbus service and all. Everything works on that side but i can't enable my user service.
    thanks!
    Last edited by nopemopes (2015-03-25 11:10:06)

    jasonwryan wrote:
    What errors are you getting? https://bbs.archlinux.org/viewtopic.php?id=57855
    Not a Sysadmin issue, moving to NC...
    sorry, didn't mean to be incomplete.
    The error says "Failed to get D-Bus connection: Connection refused".
    I did what the wiki said: Create the dbus files, enable them and such.
    No i put my service files + timer in the places mentioned by the wiki but everytime i try to enable them, that error shows up.
    systemctl status dbus gives me all good
    dbus.service - D-Bus System Message Bus
    Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
    Active: active (running) since ma 2015-03-23 19:39:24 CET; 1h 18min ago
    Docs: man:dbus-daemon(1)
    Main PID: 246 (dbus-daemon)
    CGroup: /system.slice/dbus.service
    └─246 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
    mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
    mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='...ervice'
    mrt 23 19:39:34 Jordy-Laptop dbus[246]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1....ectory.
    mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
    mrt 23 19:39:39 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
    mrt 23 19:47:01 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='...ervice'
    mrt 23 20:51:38 Jordy-Laptop dbus[246]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
    that's the log for dbus and these are my files:
    drive_sync.service
    [Unit]
    Description=Drive sync
    [Service]
    Type=simple
    ExecStart=drive_script.sh
    drive_sync.timer
    [Unit]
    Description=Drive sync
    [Service]
    Type=simple
    ExecStart=drive_script.sh
    these files are located in ~/.config/systemd/user
    Last edited by nopemopes (2015-03-23 20:00:55)

  • [SOLVED] systemd 207, lvm2 and luks booting issue

    Hi
    i'm using an encrypted lvm (luks) on my notebook.
    /boot on /dev/sda1
    lvm on    /dev/sda2
                 main-root
                 main-home
                 main-swap
    since the systemd 207 upgrade i am unable to boot my system.
    this error appears at startup:
    A start job is running for dev-mapper-main\x2droot.device
    so i'm guessing that systemd is unable to use the encrypted lvm2, since this error is aknowledged on the
    after checking some threads i tried:
    mkinitcpio -p linux
    but there was no effect.
    HOOKS="base systemd autodetect block keymap encrypt lvm2 filesystems fsck vbox
    some people tried suggesting downgrading to systemd 204 but i dont have any pkg file and building with abs leads to the following error
    while makepkg -s:
    ==> Starting prepare()...
    patching file src/core/swap.c
    Hunk #1 FAILED at 220.
    1 out of 1 hunk FAILED -- saving rejects to file src/core/swap.c.rej
    ==> ERROR: A failure occured in prepare().
    Aborting...
    am i supposed to remove the patches from the build? i'm not really sure and more of a beginner in this area.
    Can anyone help me solve either the build or the boot issue ?
    i should mention that i am only able to access my system by using chroot from an arch boot stick.
    Thank you so much.
    Kind Regards
    Last edited by ziv667 (2013-10-01 11:27:06)

    https://wiki.archlinux.org/index.php/Mk … mmon_hooks
    systemd: This will install a basic systemd setup in your initramfs, and is meant to replace the 'base', 'usr', 'udev' and 'timestamp' hooks. Other hooks (like encryption) would need to be ported, and may not work as intended. As of systemd 207, this hook does not work as intended when combined with lvm2 and may break your boot. You also may wish to still include the 'base' hook (before this hook) to ensure that a rescue shell exists on your initramfs.
    Have you tried keeping udev instead of replacing it with systemd hook?
    Have you tried https://wiki.archlinux.org/index.php/Ar … ck_Machine ? It has systemd 204.
    Last edited by karol (2013-10-01 11:16:57)

  • [SOLVED] ACPI problem - shutdown and battery error

    Hi All,
    I've installed Arch and it looks cool, but not everything work.
    I can't get acpi related infos (like battery state), or turn off my laptop. I tried hard, but i couldn't solve it.
    here are some info, if you could help me:
    -actually I can reboot flawlessly
    -i removed autodetect from the hooks list because its building lasted forever
    -lshw : http://pastebin.com/Q6Cy9Ppy
    -dmesg : http://pastebin.com/LdFTrmaC
    systemctl status systemd-udevd :
    ● systemd-udevd.service - udev Kernel Device Manager
    Loaded: loaded (/usr/lib/systemd/system/systemd-udevd.service; static)
    Active: active (running) since cs 2014-11-27 15:49:17 CET; 57min ago
    Docs: man:systemd-udevd.service(8)
    man:udev(7)
    Main PID: 136 (systemd-udevd)
    CGroup: /system.slice/systemd-udevd.service
    ├─136 /usr/lib/systemd/systemd-udevd
    ├─137 /usr/lib/systemd/systemd-udevd
    ├─138 /usr/lib/systemd/systemd-udevd
    ├─139 /usr/lib/systemd/systemd-udevd
    ├─141 /usr/lib/systemd/systemd-udevd
    ├─142 /usr/lib/systemd/systemd-udevd
    ├─143 /usr/lib/systemd/systemd-udevd
    ├─144 /usr/lib/systemd/systemd-udevd
    ├─145 /usr/lib/systemd/systemd-udevd
    └─146 /usr/lib/systemd/systemd-udevd
    nov 27 15:49:17 Arch-AcerTM4500 systemd-udevd[136]: starting version 217
    nov 27 15:50:19 Arch-AcerTM4500 systemd-udevd[136]: worker [140] /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/ACPI0001:00/ACPI0002:00 is taking a long time
    nov 27 15:50:19 Arch-AcerTM4500 systemd-udevd[136]: worker [145] /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:09/PNP0C09:00/ACPI0001:00/ACPI0002:00 is taking a long time
    nov 27 15:52:19 Arch-AcerTM4500 systemd-udevd[136]: worker [140] /devices/pci0000:00/0000:00:1f.0/PNP0C09:00/ACPI0001:00/ACPI0002:00 timeout; kill it
    nov 27 15:52:19 Arch-AcerTM4500 systemd-udevd[136]: seq 1138 '/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/ACPI0001:00/ACPI0002:00' killed
    nov 27 15:52:19 Arch-AcerTM4500 systemd-udevd[136]: worker [145] /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:09/PNP0C09:00/ACPI0001:00/ACPI0002:00 timeout; kill it
    nov 27 15:52:19 Arch-AcerTM4500 systemd-udevd[136]: seq 1060 '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:09/PNP0C09:00/ACPI0001:00/ACPI0002:00' killed
    Sorry for my strange sentences, i didn't speak or write English a long time ago.
    Last edited by vs22 (2015-02-13 09:13:17)

    I don't know why, but now it works.
    Possible reasons:
    previously I installed my system from bootstrap and now from the iso
    Arch updates
    Now I use journaling in ext4 previously not (I've installed both time to usb flash)

  • [SOLVED] systemd-arch-units conflicts with mdadm and xinetd packages

    Trying to upgrade my testing box today to latest/greatest and running into a file conflict between systemd-arch-linux providing systemd profiles for xinetd and mdadm which also think they control the same files:
    error: failed to commit transaction (conflicting files)
    /usr/lib/systemd/system/mdadm.service exists in both 'mdadm' and 'systemd-arch-units'
    /usr/lib/systemd/system/xinetd.service exists in both 'systemd-arch-units' and 'xinetd'
    Errors occurred, no packages were upgraded.
    Should I just do a force? I am not relying on systemd yet. Or should I just remove systemd?
    Chester
    Last edited by chetwisniewski (2012-05-15 18:17:45)

    silent wrote:So now the new version of mdadm and xinetd moved to [core] and I have the same conflict with systemd-arch-units in [community].
    Try -Syu again?

  • Why does labview generate Dr. Watson error "C0000005 access violation"

    I am running Labview 5.1.1 in Windows 2000 Professional on a machine with the following configuration
    *----> System Information <----*
    Computer Name: ANDANTE
    User Name: Administrator
    Number of Processors: 2
    Processor Type: x86 Family 6 Model 8 Stepping 3
    Windows 2000 Version: 5.0
    Current Build: 2195
    Service Pack: 4
    Current Type: Multiprocessor Free
    I have all of a sudden begun to experience labview crashes. The crash occurs systematically after tens of minutes; not just a few minutes, but not more than an hour or so. I am running a vi but not actively interacting with the machine (no other applications running, not even moving the mouse around). The problem happens even when running a vi that I have run successfully for extended periods of time (overnight) only 3 months ago. I have tried it with two different vis, one that I have recently made a lot of modifications to and another that has not been touched for months (since before the crashes began), and it happens with both vis. They do much different things (communicate with different GPIB or PCI boards, write to different kinds of files in different locations, etc.), so the problem seems to be vi-independent.
    When the crash occurs, I see a dialog appear with the error
    labview.exe has generated errors and will be closed by windows. You will need to restart the program. An error log has been created.
    The Dr. Watson error log is generated and the error is
    Application exception occurred:
    App: (pid=1160)
    When: 4/25/2004 @ 01:57:56.640
    Exception number: c0000005 (access violation)
    I always get the same Dr. Watson error information -- i.e., it is very reproducible. I don't really know how to interpret the rest of the Dr. Watson log, but I include the report on the first thread, which is the one with the "FAULT" in it, at the end of this email.
    Looking around on the web, it may be that a temporary virus infection could have created the problem. In the period since the machines was last successfully used, I have seen two files be infected by the W32.Welchia.B.Worm virus, the files were svchost.exe and WksPatch[1].exe. These files have been quarantined and no other infected files have been found since this error began to appear.
    Any ideas? I've seen on the web that reinstalling Windows 2000 and/or upgrading to Labview 7.0 might solve the problem, but it would be nice to get some confirmation before taking the time/spending the money.
    Here is the state dump for the thread with the FAULT in it, as provided by Dr. Watson:
    State Dump for Thread Id 0x574
    eax=00000062 ebx=00000000 ecx=00000000 edx=00000004 esi=00000000 edi=05692214
    eip=00748236 esp=0012fb28 ebp=0012fb28 iopl=0 nv up ei pl zr na po nc
    cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
    function: StrLen
    00748230 55 push ebp
    00748231 8bec mov ebp,esp
    00748233 8b4d08 mov ecx,[ebp+0x8] ss:00ba9a0e=????????
    FAULT ->00748236 8a11 mov dl,[ecx] ds:00000000=??
    00748238 8d4101 lea eax,[ecx+0x1] ds:00a79ee6=????????
    0074823b 84d2 test dl,dl
    0074823d 7407 jz GetCDReg+0x6f6 (00750c46)
    0074823f 8a10 mov dl,[eax] ds:00000062=??
    00748241 40 inc eax
    00748242 84d2 test dl,dl
    00748244 75f9 jnz CfgRemove+0x44f (0074ae3f)
    00748246 2bc1 sub eax,ecx
    00748248 48 dec eax
    00748249 5d pop ebp
    0074824a c3 ret
    *----> Stack Back Trace <----*
    FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
    0012FB28 00737A74 00000000 00000000 05692214 00000400 !StrLen
    0012FC40 00736A45 050753E4 05692214 0012FC6C 00736724 !SetKeyboardHandlerProc
    0012FC50 00736724 05692214 0012FCB4 05692214 BDBC0000 !SetKeyboardHandlerProc
    0012FC6C 00736627 05692214 0569232C 00000400 00000000 !SetKeyboardHandlerProc
    0012FC98 0074B470 0012FCB4 BDBD0001 00000000 0569E8E0 !SetKeyboardHandlerProc
    0012FCD0 0074ACD0 00000000 0074AC10 0569FFA4 010A2418 !CfgRemove
    0012FCE8 007808D5 00000000 00000000 00000001 00000000 !CfgRemove
    0012FD08 007ACEB6 00000000 00000000 77E18F95 00000000 !ChkOccurrences
    0012FD9C 006033DE 00000001 00000000 77E2ADC1 007A5C80 !WMainLoop
    0012FF24 007B2186 00400000 00000000 00000001 00000001 !WMain
    0012FFC0 7C581AF6 005C0057 0061006C 7FFDF000 C0000005 !inp
    0012FFF0 00000000 007B2030 00000000 000000C8 00000100 kernel32!OpenEventA
    *----> Raw Stack Dump <----*
    0012fb28 40 fc 12 00 74 7a 73 00 - 00 00 00 00 00 00 00 00 @...tzs.........
    0012fb38 14 22 69 05 00 04 00 00 - 16 4d 65 74 68 6f 64 20 ."i......Method
    0012fb48 4e 6f 74 20 49 6d 70 6c - 65 6d 65 6e 74 65 64 00 Not Implemented.
    0012fb58 55 1f f8 77 18 25 f8 77 - 2f a8 fd 74 c4 01 00 00 U..w.%.w/..t....
    0012fb68 05 a5 fd 74 d0 26 ce 01 - 00 00 06 01 10 04 00 00 ...t.&..........
    0012fb78 00 00 00 00 00 00 00 00 - 2e fb 69 05 42 e9 69 05 ..........i.B.i.
    0012fb88 c1 2f 7b 00 00 00 00 00 - 12 04 00 00 11 04 00 00 ./{.............
    0012fb98 30 fb 69 05 12 04 12 00 - bb 35 7b 00 00 00 06 01 0.i......5{.....
    0012fba8 11 04 00 00 00 00 00 00 - 00 00 00 00 2e fb 69 05 ..............i.
    0012fbb8 35 34 7b 00 4c 34 7b 00 - 48 00 06 01 f8 fb 12 00 54{.L4{.H.......
    0012fbc8 10 04 00 00 ec 53 07 05 - 11 04 00 00 08 fc 00 00 .....S..........
    0012fbd8 ee c8 77 00 30 fb 69 05 - 11 04 00 00 00 00 00 00 ..w.0.i.........
    0012fbe8 00 04 00 00 01 00 00 00 - ec 53 07 05 00 04 00 00 .........S......
    0012fbf8 00 38 83 00 1c fc 12 00 - 23 ca 77 00 00 38 83 00 .8......#.w..8..
    0012fc08 40 ff 69 05 01 00 00 00 - 00 00 00 00 2d 00 00 00 @.i.........-...
    0012fc18 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
    0012fc28 00 00 00 00 00 00 00 00 - 00 00 00 00 01 00 00 00 ................
    0012fc38 50 fc 12 00 1a 6a 73 00 - 50 fc 12 00 45 6a 73 00 P....js.P...Ejs.
    0012fc48 e4 53 07 05 14 22 69 05 - 6c fc 12 00 24 67 73 00 .S..."i.l...$gs.
    0012fc58 14 22 69 05 b4 fc 12 00 - 14 22 69 05 00 00 bc bd ."i......"i.....

    For questions like these, you are better off contacting NI directly. Goto www.ni.com/ask for directions. It has been my experience that Dr. Watson error logs are only useful as supplementary information. It is best for support and for the forum if you can provide a clear description on how to cause the error consistently.

  • [SOLVED]systemd and make a camera visible GUI-wise in your filemanager

    After reading a lot about systemd in the wiki and in this forum I understand there are different opionons about systemd. Anyway, I have a adapted all the changes to rc.conf leaving out only a few daemons to start there. So why not give systemd a try? If you dont want to read the full posting I finally got it to work, basically by reading carefully and checking the suggested tests in the systemd wiki. (loginctl)
    As suggested by the wiki, I tried the systemd yesterday. Enabled via systemctl some services to "replace" my rc.conf daemons. I got what I thought everything to work, including autologin directly to my Xfce4 desktop. Everything except the digital camera.
    When starting Arch traditionally via initscripts I immediately can see the camera in the filemanager (Nautilus) when the camera is attached via USB.
    Some minutes later, after adding "init=/usr/lib/systemd/systemd" to the APPEND line in Syslinux and rebooting, my machine reboots
    fine.But when connecting the camera again it is not visible graphically.
    The camera is there because when using gphoto2 (the commandline) as root I can transfer pictures etc.
    Even if I am no happy CLI user I can handle it when necessary. Handling pictures a graphical view of them is much easier...
    As the wiki about systemd says one can try it out. I have not removed anything from the system and when starting Arch again, the initscript way, I can see the camera again in my filemanager, gthumb works again and pictures can be transferred to my machine.
    In the wiki again, this time about digital cameras
    Permission issues
    Camera devices should be granted permission using ACLs. For this to work, users need to have consolekit or systemd running and the user session must be registered with them accordingly.
    Check this using /usr/bin/ck-list-sessions to verify a value of "TRUE" should be returned for both the "active" and "is-local" fields:
    $ ck-list-sessions | grep TRUE
    active = TRUE
    is-local = TRUE
    ACL=Atlantic Container Line is what first comes into my mind. I have had some connections to transport business...I admit I had to google it to find the correct interpretation of this mumbo-jumbo.
    The wiki also gives a "hint", if this is not working try to use the obsolete camera group and edit some udev rules.
    Should not be necessary when it has worked before systemd and earlier experiences
    But what is this about "Permission issues"?  Here is my listings relative the wiki hints. All seems OK.. or why the heck are there two sessions??
    [leif@krasaki ~]$ ck-list-sessions | grep TRUE
    is-local = TRUE
    active = TRUE
    is-local = TRUE
    [leif@krasaki ~]$ ck-list-sessions
    Session1:
    unix-user = '1000'
    realname = '(null)'
    seat = 'Seat1'
    session-type = ''
    active = FALSE
    x11-display = ''
    x11-display-device = ''
    display-device = '/dev/tty1'
    remote-host-name = ''
    is-local = TRUE
    on-since = '2012-10-24T07:12:56.499847Z'
    login-session-id = '1'
    idle-since-hint = '2012-10-24T07:13:26.994037Z'
    Session2:
    unix-user = '1000'
    realname = '(null)'
    seat = 'Seat1'
    session-type = ''
    active = TRUE
    x11-display = ':0'
    x11-display-device = '/dev/tty7'
    display-device = '/dev/tty1'
    remote-host-name = ''
    is-local = TRUE
    on-since = '2012-10-24T07:13:02.361157Z'
    login-session-id = '1'
    [leif@krasaki ~]$
    As one can see, the ACTIVE values are here as the wiki says. But no camera. Those values are the same, wheter which way the machine is started. But 2 sessions??
    Further reading in the systemd wiki article and consolekit vs systemd.logind gives a clue.
    From the wiki:
    In order to check the status of your user session, you can use loginctl. To see if your user session is properly set up, check if the following command contains Active=yes. All polkit actions like suspending the system or mounting external drives with Udisks should then work automatically.
    So when started via systemd and running logintctl, it gives this surprising result. Does not matter wheter as normal user, nor as root....
    [leif@krasaki ~]$ loginctl
    SESSION UID USER SEAT
    1 1000 leif seat0
    1 sessions listed.
    [leif@krasaki ~]$ loginctl show-session 1
    Id=1
    Timestamp=Wed, 24 Oct 2012 10:57:03 +0200
    TimestampMonotonic=20040019
    DefaultControlGroup=name=systemd:/user/leif/1
    VTNr=1
    TTY=tty1
    Remote=no
    Service=login
    Leader=315
    Audit=1
    Type=tty
    Class=user
    Active=no
    State=online
    KillProcesses=no
    IdleHint=yes
    IdleSinceHint=1351069009642296
    IdleSinceHintMonotonic=6664433
    Name=leif
    [leif@krasaki ~]$
    Surprising? Should it not have been Active=Yes? So something is wrong in my settings although it had worked "before" starting using systemd..
    OK, so far. Lost? Not yet. Double check again everything and I found the culprit, my  ~/.bash_profile which had worked before seemed a bit different to what is suggested in the wiki. The old one, actually started 2 sessions, as also could be seen here above checking ck-list-sessions. That was the problem
    Using a fresh edited ~/.bash_profile as suggested here, the camera is visible graphically
    Finally, just for fun, start again the old initscipt way. Enabling daemon and so on. Still 2 sessions going on....Here it was the "/.xinitrc, which also had some old fashions and I removed the ck-launch-session from the exec line. So even here, now only 1 session..
    Anyway, now the camera is visible, both starting with initscripts, naturally also some daemons active in rc.conf and by starting with systemd.
    I rest my case and it seems systemd works with everything on my machine which is just a normal desktop used by an old man.
    Thanks for reading...

    Solved now! Boot times are as fast as posssible on my HDD I think. Only thing after uninstalling initscripst and initscripts-systemd was that locale was not set inspite of a correct /etc/locale.conf. I had to make /etc/profile.d/locale.sh with this content;
    if [ -s /etc/locale.conf ]; then
    . /etc/locale.conf
    fi
    export LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE
    export LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS
    export LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION

  • Credit note is not getting generate and there is no error log

    Hi,
    Could you please help with the following scenario.
    I have created a credit memo with reference to a billing document. Then  when I try and create a credit note for this credit memo, it does not get generated and the following message apprears 'No billing documents were generated'
    Processing status for this is - 'Not Processed'
    and there are no messages in the error log as well.
    Could you please advise as to what the missing configuration might be? As i can't seem to find what is causing the problem
    Your advise is much appreciate.
    Thanks & Regards,
    Amalie

    Kindly create a Credit Memo Request wrt to Billing Document by maintaining in the Copying Control through VTAF and then create a Credit Memo wrt Credit Memo request through VTFA.
    Then go to VOFA with your Billing Type and maintain Account Determination Procedure.
    it does not get generated and the following message apprears 'No billing documents were generated'
    Do you able to get the Number while saving the Credit Memo or not able to save it .
    Kindly check the configuration of Account ket in VKOA also .
    Best Regards,
    Ankur

  • [solved] systemd-journal and shadow.pacnew updates

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

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

  • [SOLVED] systemd, autofs and lxdm

    OK, after recently migrating rc.conf to the more 'systemd' structure, but still using init I figured I'd give systemd another shot, and herein lies my problem.
    According to the wiki there should already be units available for various DMs, though i only have xdm available. I've copied and modified the copied version for lxdm (well, not strictly correctly, I've modified it to start xfce the same way that my "old" style does, with ck-launch) but I just get dumped to a root desktop (which I can't log out of). What I want is the lxdm login. I'm pretty sure there's a bunch of stuff I've forgotten since I set this up, so how do I get systemd to launch lxdm to a login screen.
    Second. I'm getting autofs errors at boot, and automounting isn't available.
    Google has helped me not one jot (either lousy googling or lousy forum thread titles, not sure which) and I need to fix this too.
    Not looking for a verbatim answer. Rather looking for links where I can get the why's and wherefore's. The Arch systemd wiki doesn't cover this (it assumed units present which are not).
    I've installed the arch units already. Any pointers would be appreciated.
    Last edited by Roken (2012-07-28 22:25:06)

    lxdm package from Community contains usr/lib/systemd/system/lxdm.service
    please check with
    pacman -Ql lxdm
    But if you can't
    systemctl enable lxdm.service
    you can try manually symlink it
    ln -s '/usr/lib/systemd/system/lxdm.service' '/etc/systemd/system/display-manager.service'
    btw. in AUR pkgbuilds there are no lxdm.service at the moment, so you neet to copy it from community source files (best way)
    Last edited by nbvcxz (2012-07-26 11:28:11)

  • I have tried downloading and installing the Adobe Pro DC trial on 2 different browsers and it keeps generating an "unexpected error". I have a MAC. How is this troubleshooted and fixed?

    I have tried downloading and installing the Adobe Pro DC trial on 2 different browsers and it keeps generating an "unexpected error". I have a MAC. How is this troubleshooted and fixed?

    Hi Carlos ,
    Could you please share the screen shot of the error message so that we can check and troubleshoot accordingly .
    Is there any error number or code associated with the error message or it just says "unexpected error" ?
    I would recommend you to try and install the Acrobat DC trial referring the following links .You could choose any of the following .Also make sure you disable all the third party software before you commence the installation .
    https://helpx.adobe.com/acrobat/kb/acrobat-downloads.html
    https://helpx.adobe.com/acrobat/kb/acrobat-dc-downloads.html
    Regards
    Sukrit Dhingra

  • EVENT 36888, Schannel A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 43. The Windows SChannel error state is 252.

    I keep losing my network connection for a few seconds at a time.  Not  a big deal unless I just spent time filling in a form and have to redo it.
    Getting:
    A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 43. The Windows SChannel error state is 252. Using windows 8.  I just installed the new ARRIS
    TG862 provided by Comcast. 
    Any Ideas?
    Also get the following errors in my events:
    The name "WORKGROUP      :1d" could not be registered on the interface with IP address 10.0.0.2. The computer with the IP address 10.0.0.3 did not allow the name to be claimed by this computer.
    Realtek PCIe GBE Family Controller is disconnected from network.
    Any help is appreciated

    Hi,
    Critical Kernel-power event ID 41 is used appear after PC restarts or randomly restarts with error
    BugcheckCode listed or a cold reboot. Do you get BSOD and some dump files?
     Default location is %SystemRoot%\Minidump. You can upload it to skydrive, then paste link here.
    How to use Skydrive
    http://www.wikihow.com/Use-SkyDrive
    Kernel-PnP event ID 219: A Plug and Play device driver on your system is failing to load due to a device driver or device malfunction, you can unplug any external devices (except mouse and keyboard, but please keep the latest drivers), and
    check device status in device manager, please also keep the all latest driver update of your PC.
    And for error 36888, I found a similar thread, please refer to this link
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/4c5430f5-43f6-41b4-97d3-03cfb3efa70b/schannel-error-event-id-36888-is-there-a-way-to-identify-what-causes-schannel-to-log-error?forum=winserverDS
    Regards
    Yolanda
    TechNet Community Support

  • Zfs scrub took forever and generated many checksum errors

    Hi,
    I have one machine running Solaris 10 10/07 X86_64. It has been a few days since I started "zpool scrub <pool>", but scrub still hasn't made much progress (still at 1.79%). I wonder if the scrub operation will ever complete. On a 4TB file system, how long does "scrub" run to finish generally?
    Also running scrub generated many checksum errors on many disks, is this normally expected? Or something is wrong with hardware?
    Any advice how to make scrub run faster?
    $ zpool status
    pool: bigpool
    state: ONLINE
    status: One or more devices has experienced an unrecoverable error. An
    attempt was made to correct the error. Applications are unaffected.
    action: Determine if the device needs to be replaced, and clear the errors
    using 'zpool clear' or replace the device with 'zpool replace'.
    see: http://www.sun.com/msg/ZFS-8000-9P
    scrub: scrub in progress, 1.79% done, 27h51m to go
    config:
    NAME STATE READ WRITE CKSUM
    bigpool ONLINE 0 0 0
    raidz1 ONLINE 0 0 0
    c3t0d0 ONLINE 0 0 16
    c3t1d0 ONLINE 0 0 14
    c3t2d0 ONLINE 0 0 12
    c3t3d0 ONLINE 0 0 16
    c3t4d0 ONLINE 0 0 6
    raidz1 ONLINE 0 0 0
    c3t5d0 ONLINE 0 0 65
    c3t6d0 ONLINE 0 0 66
    c3t7d0 ONLINE 0 0 87
    c3t8d0 ONLINE 0 0 87
    c3t9d0 ONLINE 0 0 62
    spares
    c3t10d0 AVAIL
    Simon

    what % of the 4tb is used? you could zpool scrub -s <pool> (prob know this..). zpool manpages has: "whereas scrubbing examines all
    data to discover silent errors due to hardware faults or disk failure."
    are you seeing any hw issues with disk controllers or disks themselves in /var/adm/messages since you say you have checksum errors? any fault lights on any disk or array in use?

  • Undocumented problem solved with 16-bit pcmcia and irq error

    I am having the exact same problem as described in the following post:
    "Undocumented problem solved with 16-bit pcmcia and irq error."
    "I'm using a DAQ Card (AI-16E-4), which didn't work properly in MAX. MAX complained that the card didn't respond to an interrupt request.
    I've had this issue for a while, but dropped it, since NI support told me nothing could be done about it. Meanwhile, a seemingly unrelated problem with a wireless pcmcia network card arose. Cisco had no clue what was wrong with their card either, but I found Microsoft Knowledge Base Article Q327947. It seems that Win2k (they claim SP3 and up) disables ISA to PCI routing, which is what causes this problem.
    To fix it, open regedit
    and navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Pcmcia\Parameters"
    edit or create the DWORD value "DisableIsaToPciRouting" and set the value data to 0.
    See Microsoft's article for further details: http://support.microsoft.com/default. aspx?scid=kb;en-us;327947"
    The difference is that I am using WinXP and the Regedit fix does not solve the problem. Does anybody know how he was able to continue to use the card before he solved the problem? The card works fine in MAX, but errors out in LabVIEW.

    Hey Willy,
    Here some additional suggestions that have corrected some PCMCIA difficulties in the past besides the registry edit you suggested.
    1. General Troubleshooting to Verify Correct Hardware and Software Installation
    Uninstall the PC Card hardware through Device Manager
    Remove the PC Card from the laptop
    Uninstall the NI-DAQ software
    Follow the normal installation instructions (the most important step to remember for Plug-n-Play Operating Systems is to install the software first)
    Try the latest service packs for Win 2000 or Win XP
    Try the PC Card in a different laptop
    Try a different slot in the laptop. On certain laptops PC Cards have been successfully installed in the top PCMCIA slot instead of the bottom.
    2. Additional Troubleshootin
    g for PC Cards that Return IRQ Conflicts
    For E-Series DAQCards:
    Update to NI-DAQ 6.9.3 first and then update NI-PAL to version 1.6.1 (included exe file).
    Download the attached NI-PAL (ni-cdu1610.exe), and run the installer. When receiving the error "The device is not responding to the first IRQ Level" in Measurement and Automation Explorer, try this method of upgrading NI-PAL
    3. Additional Troubleshooting Steps
    Try disabling the 3COM adapter, and any other extraneous (for now) devices like any built in serial and parallel ports. The best way to do this is probably to disable them in the BIOS. If the PCMCIA card works properly then try to reconfigure disabled devices one at a time.
    Make sure the latest BIOS is installed.
    Check for any unusual PCMCIA drivers or other software that might interfere with the PCMCIA driver.
    I hope this helps.
    Ron
    Applications Engineering
    National Instruments
    Attachments:
    ni-cdu1610.exe ‏1557 KB

Maybe you are looking for