similar to: use pssh to restart a service

> > What does the sudo log say? This is all the secure logs say about the ssh session: [root at logs:~] #tail -f /var/log/secure Oct 31 19:15:20 logs sshd[24407]: Accepted publickey for bluethundr from 47.18.111.100 port 47469 ssh2: RSA ae:62:1f:de:54:89:af:2c:10:16:0e:fd:8d:7e:81:06 Oct 31 19:15:21 logs sshd[24407]: pam_unix(sshd:session): session opened for user bluethundr by (uid=0)

> > Have you tried running the command from a conventional login? > sudo -S > expects a password from stdin, where is that being supplied? Yep! That works fine. #ssh -qt bluethundr at es1.example.com "/bin/sudo -S /bin/systemctl restart elasticsearch" #ssh -qt bluethundr at es1.example.com "/bin/echo $?" 0 And the user has 'NOPASSWD' access. Any

Hey Gordon, Sorry, man my bad! Disabling the tty requirement for my sudo user does indeed work. I had a type-o in the sudoers file, and when I corrected it, my sudo command via pssh started working! #pssh -i -h es_list "/bin/sudo /bin/systemctl restart elasticsearch; sleep 10" [1] 20:31:32 [SUCCESS] bluethundr at es3.jokefire.com Stderr: sudo: sorry, you must have a tty to run sudo

On Sat, Oct 31, 2015 at 5:04 PM, Tim Dunphy <bluethundr at gmail.com> wrote: > Hi all, > > I need to restart a service on a few elasticsearch nodes. I'm trying to do > it with pssh. > > I'm getting this error when I try to do that: > > pssh -h es_list "/bin/sudo -S /bin/systemctl restart elasticsearch" > [1] 17:01:50 [FAILURE] bluethundr at

On 10/31/2015 02:04 PM, Tim Dunphy wrote: > pssh -h es_list "/bin/sudo -S /bin/systemctl restart elasticsearch" The default configuration prohibits use if input echo can't be disabled. That means no "-S". I modify that for users where necessary: /etc/sudoers.d/myuser: Defaults:myuser !requiretty, visiblepw

Hey guys, My NFS server has been working really well for a long time now. Both client and server run CentOS 7.2. However when I just had to remount one of my home directories on an NFS client, I'm now getting the error when I run mount -a mount.nfs: an incorrect mount option was specified This is the corresponding line I have in my fstab file on the client:

On 10/31/2015 04:16 PM, Tim Dunphy wrote: > Got the same exact message! > > Anything else I can try? I think you need to double-check your sudoers file. Use the '-i' argument to pssh to get more information. # cat /etc/sudoers.d/gordon gordon ALL=(ALL) NOPASSWD: ALL $ pssh -h t -i sudo echo true [1] 16:02:12 [FAILURE] MYHOST Exited with error code 1 Stderr: sudo: sorry,

I've got a Cento 6.2 server I'm putting together that will become a mailserver. It will have on it MailScanner and MailWatch for MailScanner. I'm using the latest stuff available and have run into a problem with changes I need to make in the /etc/sudoers file. It doesn't seem to take affect after I make the changes, so either the syntax within the file has changed or the way

Hi to all. I'm having a problem with the rpm command on centos 5.5; I am used to recompile a source rpm with the following command: root at test ~: rpmbuild --rebuild pssh-1.2.2-1.rf.src.rpm Installing pssh-1.2.2-1.rf.src.rpm error: cannot create %sourcedir /home/test/rpm/SOURCES error: pssh-1.2.2-1.rf.src.rpm cannot be installed Does anybody know something about that ? Thanks in

Hi Marc On 17/02/15 09:40, Marc Dietrich wrote: > This adds clang/gcc visibility macro detection to configure and util/macros.h. > This is can be used to conveniently add e.g. a "HIDDEN" attribute to a function. > I believe this should be OK to go in regardless of the status of patch 2. There are just a couple of trivial nitpicks. > Signed-off-by: Marc Dietrich

On 02/11/15 12:35, Tim Dunphy wrote: > Hey Gordon, > > Sorry, man my bad! Disabling the tty requirement for my sudo user does > indeed work. I had a type-o in the sudoers file, and when I corrected it, > my sudo command via pssh started working! > This is why it is paramount to use visudo command as opposed editing the /etc/sudoers file directly! The visudo command will check

On Sun, Oct 02, 2016 at 11:42:41PM -0400, Tim Dunphy wrote: > Hey guys, > > My NFS server has been working really well for a long time now. Both > client and server run CentOS 7.2. > > However when I just had to remount one of my home directories on an NFS > client, I'm now getting the error when I run mount -a > > mount.nfs: an incorrect mount option was

Hello Everybody, I am looking for a way to trigger puppet rum remotely. so that i don''t need to login into individual nodes and perform the puppet agent --test from there. Is there any alternative to puppet kick in puppet 3.0, since its being deprecated in telly. Also , can anybody tell how to configure foreman 1 to trigger puppet run from the gui in puppet

G'Day All, Can anyone give me some direction in setting up the TFTP server on my RadHat ES3 box? I did quite a bit of reading, but I think I am more unsure now than before. I found the information nebulous. TFTP is already installed. I am trying to determine where the root directory for the tftp services is located so I can copy the CISCO 7960 firmware files onto it. Thanks.... Ferg

Hey guys, I have this log rotation script setup in my /etc/logrotate.d folder /var/log/elasticsearch/*.log { daily rotate 100 size 50M copytruncate compress delaycompress missingok notifempty create 644 elasticsearch elasticsearch } And I notice that log files are still being generated that are upwards of 7 or 8 GBs. Can anyone point out to me where the

G'Day All What do I type at the command line to stop and start * on a RedHat ES3 box? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20041202/f9c92727/attachment.htm

Hi all, I have recently worked on fts plugin for ElasticSearch. https://github.com/filiphanes/fts-elastic It is forked from fts-elasticsearch as you can see in PR https://github.com/atkinsj/fts-elasticsearch/pull/21 with following changes (maybe some more) - no duplicate json keys in indexed documents, so compatible with ES 7.x - 1 elastic index for all users with routing by username -

Am 19.02.2019 um 13:55 schrieb Ionut Hoza: > Hi Ralf, > > You should check you firewall configuration ... most probably you need to > allow port 9200. > Also check if elasticsearch service is listening on all interfaces or just > localhost (127.0.0.1). Hallo, the firewall is disabled. I tried several variations in the config-file. 0.0.0.0 192.168.242.4 Only 127.0.0.1 is

Hallo, is anyone here using elasticsearch on centos? I tried several configs to configure external access but nothing is working. My tests: telnet localhost or 127.0.0.1 9200 works local on the machine telnet 192.168.242.4 9200 connection refused local on the machine. So it is clear that access from other systems can not work. Is there perhaps something special to consider when using centos 7?

Hi, I was experimenting with Logstash + elasticsearch on FreeBSD 9 - initially I downloaded it by hand (I forgot to check for a port) and it worked fine. I then tried the port and this forced me to use a different java version (was jdk-16.0.3p4_25 now openjdk6-b27) and it seems that the new one causes a panic. Unfortunately crashdumps aren't working properly, however I did get the panic