search for: timeoutsec

...putfont: 512,8x16: failed: -1 Sep 12 19:41:12 myhost systemd-vconsole-setup[84]: putfont: PIO_FONT: Invalid argument Sep 12 19:41:12 myhost systemd-vconsole-setup[117]: /usr/bin/setfont failed with error code 71. Sep 12 19:41:13 myhost systemd[1]: [/etc/systemd/system.conf:15] Unknown lvalue 'TimeoutSec' in section 'Manager' The former errors might be normal on a system with no VGA, and you mentioned seeing this over serial.? Do you see those errors on systems that boot normally?? Do any of those system share a hardware configuration with the system that doesn't? The latter er...

Hi, Let me cite the service file here: [Unit] Description=/etc/rc.d/rc.local Compatibility ConditionFileIsExecutable=/etc/rc.d/rc.local After=network.target [Service] Type=forking ExecStart=/etc/rc.d/rc.local start TimeoutSec=0 RemainAfterExit=yes I basically don't understand two things here: 1. What makes it run? Sure, when I make /etc/rc.d/rc.local executable, it runs. But for all I know, for it to run some other service must pull in it as a dependency. Am I wrong? 2. Why Type=forking? Thanks in advance. Rega...

...n.target After=network-online.target systemd-journald-dev-log.socket nss-lookup.target local-fs.target remote-fs.target dahdi.service misdn.service lcr.service wanrouter.service mysql.service postgresql.service Wants=network-online.target Conflicts=shutdown.target [Service] Type=forking Restart=no TimeoutSec=5min IgnoreSIGPIPE=no KillMode=process GuessMainPID=no RemainAfterExit=yes SysVStartPriority=2 ExecStart=/etc/init.d/asterisk start ExecStop=/etc/init.d/asterisk stop ExecReload=/etc/init.d/asterisk reload My /etc/init.d/asterisk file is sourcing my /etc/default/asterisk which includes an (uncomm...

> Let me cite the service file here: > > [Unit] > Description=/etc/rc.d/rc.local Compatibility > ConditionFileIsExecutable=/etc/rc.d/rc.local > After=network.target > > [Service] > Type=forking > ExecStart=/etc/rc.d/rc.local start > TimeoutSec=0 > RemainAfterExit=yes > > I basically don't understand two things here: > > 1. What makes it run? Sure, when I make /etc/rc.d/rc.local executable, > it runs. But for all I know, for it to run some other service must > pull in it as a dependency. Am I wrong? It will be...

Hi All - I have a systemd service file to start my application. Part of my service file is: [Service] Type=forking ExecStart=/path to start ExecStop=/path to stop RemainAfterExit=yes This works fine "normally". However - when I do a "yum update; and reboot" my script detects a kernel change and now does a number of "recompiling" steps for drivers and such before

...ne (killing the existing one). It did this multiple times. When trying to systemd I see a bunch of zombie processes that used to be snmp-ups for one of ups2-1 or ups3-1 (depending on the run). I'm trying again with /etc/systemd/system/nut-driver.service.d/nut-driver.conf set to: [Service] TimeoutSec=600 and /etc/ups/ups.conf having maxretry = 10 retrydelay = 15 This time ps shows three apparently happy snmp-ups processes but upsdrvctl start is still showing up. ... and then everything vanishes but systemd doesn't complain. journalctl -xe shows a good startup then claims nut-driver.se...

.../lib/systemd/system/ovirt-firstboot.service << \EOF_firstboot -[Unit] -Description=firstboot configuration program (text mode) -After=livesys.service plymouth-quit.service -Before=systemd-user-sessions.service - -[Service] -Environment=RUNLEVEL=3 -ExecStart=/etc/init.d/ovirt-firstboot start -TimeoutSec=0 -RemainAfterExit=yes -Type=oneshot -SysVStartPriority=99 -StandardInput=tty - -[Install] -WantedBy=multi-user.target -EOF_firstboot - -systemctl enable ovirt-firstboot.service >/dev/null 2>&1 - - -echo "Configuring IPTables" -# here, we need to punch the appropriate holes in t...

...s-lookup.target local-fs.target remote-fs.target dahdi.service >> misdn.service lcr.service wanrouter.service mysql.service postgresql.service >> Wants=network-online.target >> Conflicts=shutdown.target >> >> [Service] >> Type=forking >> Restart=no >> TimeoutSec=5min >> IgnoreSIGPIPE=no >> KillMode=process >> GuessMainPID=no >> RemainAfterExit=yes >> SysVStartPriority=2 >> ExecStart=/etc/init.d/asterisk start >> ExecStop=/etc/init.d/asterisk stop >> ExecReload=/etc/init.d/asterisk reload >> >> &gt...

On 9/11/20 5:29 PM, Quinn Comendant wrote: > Those have always reported success (even before I removed the OnFailure option): In that case, I'd revert the change you made, unlock the root account so that you can use the emergency shell, let the system boot to an emergency shell, and collect the output of "systemctl status initrd-parse-etc.service" and "journalctl -b

...from the default in the RPM. By "working" I mean it starts after reboot and after issuing 'sudo systemctl restart nut-driver' but, as expected, it takes quite a while to finish startup. /etc/systemd/system/nut-driver.service.d/nut-driver.conf [Unit] StopWhenUnneeded=no [Service] TimeoutSec=600 /etc/ups/ups.conf ... maxretry = 10 retrydelay = 15 ... As I said, I suspect the bulk of these are cargo cult "it worked, not messing with it" settings. nomad

Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of systemd but

...unt Home-Users [Automount] Where=/home/users [Install] WantedBy=multi-user.target systemctl cat home-users.mount # /etc/systemd/system/home-users.mount [Unit] Description=User Homes [Mount] What=hostname.internal.domain.tld:/users Where=/home/users Type=nfs4 Options=sec=sys #Options=sec=krb5i TimeoutSec=150 [Install] WantedBy=multi-user.target And enable it. systemctl enable home-users.mount systemctl enable home-users.automount systemctl start home-users.automount The key here is, home-users.mount home-users.automount The part "home-user" MUST reflect the real path. This should...

On 01/04/2020 12:20, L.P.H. van Belle via samba wrote: > For that to work, you need to add the CIFS/hostname.fqdn at REALM to the host your logging in. > The COMPUTER$ should hold it. > Allow the computer to delegate the cifs service. ( or all ) Thing is, the OP is trying to use a users ticket to mount, but seems to be doing it as root, which isn't going to work, mainly because

...rter at .service [Unit] Description=VBox Virtual Machine %i Service Requires=systemd-modules-load.service vboxballoonctrl-service.service After=systemd-modules-load.service vboxballoonctrl-service.service Conflicts=shutdown.target [Service] User=<username> Group=vboxusers Restart=on-failure TimeoutSec=5min Environment="VBOX_USER_HOME=/home/rkampen/VirtualBox VMs/%i" ExecStart=/usr/bin/VBoxHeadless -s %i ExecStop=/usr/bin/VBoxManage controlvm %i savestate [Install] WantedBy=multi-user.target and on occasions the invocation systemctl start vboxvmstarter at Windoze10_2.service will work...

...I reran "service xendomains start" and it finished the job. So, is there a built in timeout of ~5 minutes here that I need to increase? I see that the generated /run/systemd/generator.late/xendomains.service file contains: . . [Service] Type=forking Restart=no TimeoutSec=5min . . So that's probably what is being hit, but I cannot work out how to make the generator apply a longer timeout. Any hints would be appreciated. Cheers, Andy -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'),...

Hi, Thank you for replying. User home directory creation is working without the need to edit /etc/pam.d/common-session The logon script I mentioned here is a in-house script to handle directory mounting for file server access, and create shortcut on the account desktop for different logins. On my Linux machines, currently all is done manually by local user account creation and by adding the

.../system/glusterfsmounts.service [Unit] Description=Glustermounting Requires=glusterd.service Wants=glusterd.service After=network.target network-online.target glusterd.service [Service] Type=simple RemainAfterExit=true ExecStartPre=/usr/sbin/gluster volume list ExecStart=/bin/mount -a -t glusterfs TimeoutSec=600 SuccessExitStatus=15 Restart=on-failure RestartSec=60 StartLimitBurst=6 StartLimitInterval=3600 [Install] WantedBy=multi-user.target After create it remember to reload the systemd daemon like: systemctl enable glusterfsmounts.service systemctl demon-reload Also, I am using /etc/fstab to moun...

On Tue, Sep 6, 2016 at 1:55 AM, Olivier <oza.4h07 at gmail.com> wrote: > Hello, > > After testing "pkill -SEGV -f /usr/sbin/asterisk" on Debian Jessie > platform, I've got several questions : > > > 1. When I issue a "cd /tmp; asterisk -cvvvvvvvvvvvg -U asterisk -G > asterisk" command, and then issue a "pkill -SEGV asterisk" command,

I was used to integrate some linux client in my samba network mounting homes with 'unix extensions = yes', and works as expected, at least with some old lubuntu derivatives. Client side i use 'pam_mount'. Now i'm working on a ubuntu mate derivative, and i've not found a way to start the session properly in CIFS. If i create a plain local home (pam_mkhome), session start as

Hi Chris, here is a link to the settings needed for VM storage: https://github.com/gluster/glusterfs/blob/03592930239c3b43cbbdce17607c099ae075fd6d/extras/group-virt.example#L4 You can also ask in ovirt-users for real-world settings.Test well before changing production!!! IMPORTANT: ONCE SHARDING IS ENABLED, IT CANNOT BE DISABLED !!! Best Regards,Strahil Nikolov? On Mon, Jun 5, 2023 at 13:55,