search for: auxww

On 12/03/2016 09:36 AM, Charles Lepple wrote: >> On Dec 3, 2016, at 9:44 AM, Jack McGee <jack at greendesk.net> wrote: >> >> But doesn't this still indicate an error: >> >> mythuser at amethi:/etc/nut$ upscmd -l CyberPower1 >> Error: Connection failure: Connection refused > Correct - "upsc", "upscmd" and "upsrw" need to

Hi Martin, > Does a useful ps command (e.g. ps auxww) show smbd running? What do > the smbd logs say? no, root at ctdb-<HOST>:~# ps auxwww | grep smbd root     13192  0.0  0.0  12780   940 pts/0    S+   13:05   0:00 grep smbd There is no smbd, nmbd is running. Ahh, but the log says: [2019/05/16 11:26:38.702593,  0] ../source3/smbd/serv...

> Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only >write a PID file when the driver goes into the background, and "-D" prevents that. I don't see another usbhid-ups running ... unless its "hidden".... I would have to install the unhide package then.... /var/run/devd.pid

On 12/03/2016 10:08 AM, Charles Lepple wrote: >> On Dec 3, 2016, at 11:01 AM, Jack McGee <jack at greendesk.net> wrote: >> >> I did restart those services, no change. >> > $ ps auxww|grep [/]nut > root 13074 0.0 0.0 37844 2628 ? Ss 08:42 0:00 /lib/nut/upsmon > nut 13076 0.0 0.0 45632 5148 ? S 08:42 0:00 /lib/nut/upsmon > nut 13176 0.0 0.0 30928 2228 ? Ss 08:42 0:01 /lib/nut/tripplite_usb -a tl > nut 13...

...to occur at 2pm - not good…) This production server had around 400 concurrent users when at the time it failed this time. In order to get it to start servicing users again I tried to kill the “Winbindd” daemons using “pkill winbindd” and all but one of the daemons died: > root at filur05# ps auxww | egrep winbind > root 1550 0.0 0.0 271956 127236 - S 07:12 0:23.66 winbindd: domain child [AD] (winbindd) > root 29659 0.0 0.0 237240 122108 - I 10:04 0:00.02 winbindd: domain child [FILUR05] (winbindd) > root 99774 0.0 0.1 267384 14302...

...6 I have enabled access via /etc/hosts.allow: > cat /etc/hosts.allow | grep slapd slapd: ALL I can see the server running and listening on port 636: > netstat -l | grep ldaps tcp 0 0 *:ldaps *:* LISTEN tcp 0 0 *:ldaps *:* LISTEN > ps auxww | grep slapd ldap 21865 0.0 0.2 467976 5860 ? Ssl 19:54 0:02 /usr/sbin/slapd -h ldap:/// ldaps:/// -u ldap I am missing something very obvious. Can anyone offer any clues? Thanks. -- Paul (ganci at nurdog.com)

I have an APC Back-UPS CS 500 which connects via USB. I am running NUT 2.4.1 under Karmic amd64. The entry in ups.conf is [apc] driver = usbhid-ups port = auto desc = "APC Back-UPS CS 500" I left upsd.conf at the default values, nut.conf is "mode standalone", and in upsmon.conf, the monitor line is MONITOR apc at localhost 1 ups_local mypassword master and in upsd.users,

I''ve created a couple of tasks in my deploy.rb file for starting and stopping backgroundrb on the remote server. The stop task runs fine and kills the process. And the start task *seems* to run successfully, but backgroundrb is never started on the remote host. Has anyone had success with this? Here are my deploy tasks: desc ''Start backgroundrb server (default

...e. So I wondered if that can make a difference. If I stop winbind, and restart samba... # /etc/init.d/samba restart [ ok ] Restarting nmbd (via systemctl): nmbd.service. [ ok ] Restarting smbd (via systemctl): smbd.service. [ ok ] Restarting samba-ad-dc (via systemctl): samba-ad-dc.service. # ps auxww | grep winbind root 19867 0.0 0.0 12764 948 pts/0 S+ 14:13 0:00 grep winbind Then I can connect with smbclient to the system where I never could before. That would be fine except that ssh requires winbind. If I stop /etc/init.d/samba and launch nmbd, smbd and winbind as services on...

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1

Hi everybody, I just updated my ctdb node from Samba version 4.9.4-SerNet-Debian-11.stretch to Samba version 4.9.8-SerNet-Debian-13.stretch. After restarting the sernet-samba-ctdbd service the node doesn't come back and remains in state "UNHEALTHY". I can find that in the syslog: May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445 May 16

...======================== Kernel options ========================== # # Network File Systems # # CONFIG_CODA_FS is not set CONFIG_NFS_FS=y # CONFIG_NFSD_SUN is not set CONFIG_SUNRPC=y CONFIG_LOCKD=y CONFIG_SMB_FS=y # CONFIG_SMB_WIN95 is not set # CONFIG_NCP_FS is not set ======================== ps auxww after startup ================== root 239 0.0 0.4 1224 628 ? S 22:57 0:00 /usr/local/samba/bin/smbmount //rex/c XXXXXXXXXXXXXX -n net_guest -U net_guest -N -c mount /smb/rex/c root 255 0.0 0.4 1224 628 ? S 22:57 0:00 /usr/local/samba/bin/smbmount //kate/c XXXXXX...

On Wed, Apr 01, 2020 at 03:33:00PM -0700, Jeremy Allison via samba wrote: > On Wed, Apr 01, 2020 at 02:09:57PM -0700, Alexey A Nikitin via samba wrote: > > Hi, > > > > Recently I by mistake ran `wbinfo -u <username>` when I was actually intending to run `wbinfo -n <username>`. It ignored the <username> part and proceeded to fetch the usernames. On a small

...ws that the filesystem is mounted rw. The server has it exported rw to the entire subnet. Other machines (CentOS 5) mount the same filesystems without a problem. Looks a lot like an idmapd issue, right? On the server: # id joe uid=501(joe) gid=501(joe) groups=501(joe) Back on the client: $ ps auxww | grep idmap | grep -v grep $ id joe uid=1000(joe) gid=1000(joe) groups=1000(joe) $ cd /nfs $ ls -n drwx------. 6 1000 1000 4096 Apr 23 11:20 one drwxr-xr-x. 4 1000 1000 4096 Dec 14 2011 two So it looks like even though the name/UID mapping is correct even though the idmapd daemon isn't run...

...winbind, and restart samba... > > > > # /etc/init.d/samba restart > > [ ok ] Restarting nmbd (via systemctl): nmbd.service. > > [ ok ] Restarting smbd (via systemctl): smbd.service. > > [ ok ] Restarting samba-ad-dc (via systemctl): samba-ad-dc.service. > > # ps auxww | grep winbind > > root 19867 0.0 0.0 12764 948 pts/0 S+ 14:13 0:00 grep > > winbind > > > > This shows that 'winbindd' isn't running, if I run a similar command on > a domain member: > > rowland at devstation:~$ ps ax | grep winbind >...

...ib/Support/CMakeFiles/LLVMSupport.dir/ARMWinEH.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Allocator.cpp.o [ 0%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/BlockFrequency.cpp.o And while doing that I ran this and see it's running /usr/bin/c++: $ ps auxww | grep LLVMSupp stark 26435 0.1 0.0 10400 2744 pts/6 S+ 18:50 0:00 make -f lib/Support/CMakeFiles/LLVMSupport.dir/build.make lib/Support/CMakeFiles/LLVMSupport.dir/build stark 26463 0.0 0.0 4328 752 pts/6 S+ 18:50 0:00 /bin/sh -c cd /home/stark/src/llvm-build/lib/Suppo...

I'm using Nas4Free, and I'm getting the following message all the time in the Daemon log: usbhid-ups[42466]: libusb_get_report: Unknown Error I'm running Nas4Free 9.2.0.1 Shigawire Driver usbhid-ups Nut Version is 2.7.1 Internal verion 0.38 UPS Info from Nas4Free Manufacturer:CP1500PFCLCD Model:CRCA102*AF1 The model UPS I'm running is a Cyber Power CP1500PFCLCD, other

...can't have more than one usbhid-ups process talking to the same UPS at one time - regardless of whether they write a PID file. In the case of running with "-D", you would need to double-check for any in the background (and there was a PID file named usbhid-ups-upstl1300.pid). "ps auxww|grep [u]sbhid-ups" should show only one driver in either case. Still looking into the altsetting issue. I would have to shuffle a few machines around to get a copy of 10.2 running on a box that isn't being actively used for anything else, but maybe there is something in their source contr...

> On Dec 3, 2016, at 11:01 AM, Jack McGee <jack at greendesk.net> wrote: > > I did restart those services, no change. > $ ps auxww|grep [/]nut root 13074 0.0 0.0 37844 2628 ? Ss 08:42 0:00 /lib/nut/upsmon nut 13076 0.0 0.0 45632 5148 ? S 08:42 0:00 /lib/nut/upsmon nut 13176 0.0 0.0 30928 2228 ? Ss 08:42 0:01 /lib/nut/tripplite_usb -a tl nut 13178 0.0 0.0 37844...

..., I'll byte, the only usnhid-ups on the system is on the old wheezy > drive, and its a 32 bit so won't run on a 64 bit install. ?? Per https://alioth-lists.debian.net/pipermail/nut-upsuser/2019-May/011389.html I thought you reinstalled NUT, and that was fixed? At this point, "ps auxww | grep usbhid-ups" should return nothing (except maybe the grep command itself). Then try this as root: /lib/nut/usbhid-ups -a myups -DD (The "myups" name was based on an earlier email; please adjust if /etc/nut/ups.conf contains a different UPS name.)