Sorry, forgot the âc. Iâm running clogin for some diagnostic stuff, but the same principle applies:
su -l -c "clogin -x stackstate-error-cmds.txt ${device}" rancid
--Chris
Chris GauthierSenior Network Engineer | comScore, Inc.
o +1 503-331-***@comscore.com
317 SW Alder St, Suite 500 | Portland | OR97204
............................................................................................................................................................................................................................
From: Vacheslav <***@skno.by>
Date: Tuesday, October 3, 2017 at 7:49 AM
To: "Gauthier, Chris" <***@comscore.com>, 'Alexander Griesser' <***@anexia-it.com>, "rancid-***@shrubbery.net" <rancid-***@shrubbery.net>
Subject: RE: [rancid] problem with rancid crontab
~ # su âl â/tmp/test.shâ rancid
No passwd entry for user 'âl'
From: Gauthier, Chris [mailto:***@comscore.com]
Sent: Tuesday, October 3, 2017 5:44 PM
To: Vacheslav <***@skno.by>; 'Alexander Griesser' <***@anexia-it.com>; rancid-***@shrubbery.net
Subject: Re: [rancid] problem with rancid crontab
I fixed that by running:
su âl â/tmp/test.shâ rancid
The â-lâ says to make it a login shell so the environment variables will load.
--Chris
Chris Gauthier
Senior Network Engineer
|
comScore, Inc.
o +1
503-331-2704<tel:503-331-2704>
***@comscore.com<mailto:***@comscore.com>
317 SW Alder St, Suite 500 | Portland | OR 97204
............................................................................................................................................................................................................................
From: Rancid-discuss <rancid-discuss-***@shrubbery.net<mailto:rancid-discuss-***@shrubbery.net>> on behalf of Vacheslav <***@skno.by<mailto:***@skno.by>>
Date: Tuesday, October 3, 2017 at 7:37 AM
To: 'Alexander Griesser' <***@anexia-it.com<mailto:***@anexia-it.com>>, "rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>" <rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>>
Subject: Re: [rancid] problem with rancid crontab
Well it didnât run because when I su rancid and execute:
/root $ /tmp/test.sh
bash: /tmp/test.sh: /bin/sh^M: bad interpreter: No such file or directory
running: sh /tmp/test.sh
produces a log file with the following content:
/root
How to fix the script?
From: Alexander Griesser [mailto:***@anexia-it.com]
Sent: Tuesday, October 3, 2017 4:53 PM
To: Vacheslav <***@skno.by<mailto:***@skno.by>>; rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>
Subject: AW: [rancid] problem with rancid crontab
Iâm not sure if your answer means that the problem is solved now or not; if it isnât, please add the following testscript as a cronjob and check the output:
Create the file â/tmp/envtest.shâ with the following content:
#!/bin/sh
export > /tmp/envtest.log
set >> /tmp/envtest.log
pwd >> /tmp/envtest.log
Save it and run `chmod 755 /tmp/envtest.sh`.
Add the following line to your crontab:
0 * * * * rancid /tmp/envtest.sh
Wait a minute and check /tmp/envtest.log; you should see the environment and current working directory in the logfile then which might help to diagnose this issue.
Best,
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: ***@anexia-it.com<mailto:***@anexia-it.com>
Web: http://www.anexia-it.com<http://www.anexia-it.com/>
Anschrift Hauptsitz Klagenfurt: FeldkirchnerstraÃe 140, 9020 Klagenfurt
GeschÀftsfÌhrer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Vacheslav [mailto:***@skno.by]
Gesendet: Dienstag, 3. Oktober 2017 15:45
An: Alexander Griesser <***@anexia-it.com<mailto:***@anexia-it.com>>; rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>
Betreff: RE: [rancid] problem with rancid crontab
Well if it were properly set, the error would be clear.
rancid:x:103:101:added by portage for rancid:/var/rancid:/bin/bash
Thanks for the answer.
From: Alexander Griesser [mailto:***@anexia-it.com]
Sent: Tuesday, October 3, 2017 4:16 PM
To: Vacheslav <***@skno.by<mailto:***@skno.by>>; rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>
Subject: AW: [rancid] problem with rancid crontab
Hi,
You can set the CWD to ~rancid first and then execute ârancid-runâ, but this is (at least to my experience) not necessary if the home directory for your rancid user iss et properly in /etc/passwd.
What does `grep rancid /etc/passwd` return on your system? Is /var/rancid liste das the home directory for this account?
Best,
Alexander Griesser
Head of Systems Operations
ANEXIA Internetdienstleistungs GmbH
E-Mail: ***@anexia-it.com<mailto:***@anexia-it.com>
Web: http://www.anexia-it.com<http://www.anexia-it.com/>
Anschrift Hauptsitz Klagenfurt: FeldkirchnerstraÃe 140, 9020 Klagenfurt
GeschÀftsfÌhrer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601
Von: Rancid-discuss [mailto:rancid-discuss-***@shrubbery.net] Im Auftrag von Vacheslav
Gesendet: Dienstag, 3. Oktober 2017 14:23
An: rancid-***@shrubbery.net<mailto:rancid-***@shrubbery.net>
Betreff: [rancid] problem with rancid crontab
Peace,
I configured crontab as root as such:
0 */6 * * * rancid /usr/bin/rancid-run
# Clean out config differ logs5
0 23 * * * rancid /usr/bin/find /var/rancid/logs -type f -mtime +2 -exec rm {} \
But an error is logged:
clogin error: Error: password file (//.cloginrc) does not exist
I do not understand what the path // is. The .cloginrc file is in /var/rancid
Or is it absolutely necessary to run cron as user rancid?
p.s Iâm using rancid 3.7