search for: tapn

...,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:25:90:25:ae:27 brd ff:ff:ff:ff:ff:ff inet 141.211.201.7/24 brd 141.211.201.255 scope global eth1 inet6 fe80::225:90ff:fe25:ae27/64 scope link valid_lft forever preferred_lft forever results of netstat -tapn | grep smb [root at nuit-filer01 ~]# netstat -tapn | grep smb | sed 's/141.211/10.211/g' tcp 0 0 :::139 :::* LISTEN 4026/smbd tcp 0 0 :::445 :::* LISTEN 4026/smbd tcp 0 0 ::ffff:10.211.68.143:445 ::fff...

...? ?Y ? ? ? 28777 ?Task Status of Volume public ------------------------------------------------------------------------------ There are no active volume tasks ??However the active process is STILL the same pid AND still listening on the old port ?root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster tcp ? ? ? ?0 ? ? ?0 0.0.0.0:49152 ? ? ? ? ? 0.0.0.0:* ? ? ? ? ? ? ? LISTEN ? ? ?5913/glusterfsd ??The other nodes logs fill up with errors because they can't reach the daemon anymore. They try to reach it on the "new" port instead of the old one: ?[2017-09-21 08:33:25.2...

----- V?stule no Rowland Penny <rowlandpenny at googlemail.com> --------- Datums: Fri, 20 Mar 2015 09:19:10 +0000 S?t?t?js: Rowland Penny <rowlandpenny at googlemail.com> Temats: Re: [Samba] Samba AD DC and browsing of shares Sa??m?js: samba at lists.samba.org >>> You can recompile it if you want to, but if you use packages from >>> your distro, you

...blic > ------------------------------------------------------------ > ------------------ > There are no active volume tasks > > > However the active process is STILL the same pid AND still listening on > the old port > > root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster > tcp 0 0 0.0.0.0:49152 0.0.0.0:* > LISTEN 5913/glusterfsd > > > The other nodes logs fill up with errors because they can't reach the > daemon anymore. They try to reach it on the "new" port instead of the old > one: >...

...? ?Y ? ? ? 28777 ?Task Status of Volume public ------------------------------------------------------------------------------ There are no active volume tasks ??However the active process is STILL the same pid AND still listening on the old port ?root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster tcp ? ? ? ?0 ? ? ?0 0.0.0.0:49152 ? ? ? ? ? 0.0.0.0:* ? ? ? ? ? ? ? LISTEN ? ? ?5913/glusterfsd ??The other nodes logs fill up with errors because they can't reach the daemon anymore. They try to reach it on the "new" port instead of the old one: ?[2017-09-21 08:33:25.2...

...ublic > > ------------------------------------------------------------------------------ > There are no active volume tasks > > > However the active process is STILL the same pid AND still listening on > the old port > > root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster > tcp 0 0 0.0.0.0:49152 0.0.0.0:* > LISTEN 5913/glusterfsd > > > The other nodes logs fill up with errors because they can't reach the > daemon anymore. They try to reach it on the "new" port instead of the old > one: >...

...blic > ------------------------------------------------------------ > ------------------ > There are no active volume tasks > > > However the active process is STILL the same pid AND still listening on > the old port > > root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster > tcp 0 0 0.0.0.0:49152 0.0.0.0:* > LISTEN 5913/glusterfsd > > > The other nodes logs fill up with errors because they can't reach the > daemon anymore. They try to reach it on the "new" port instead of the old > one: >...

...me public > ------------------------------------------------------------------------------ > There are no active volume tasks > > > However the active process is STILL the same pid AND still listening on the old port > > root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster > tcp 0 0 0.0.0.0:49152 0.0.0.0:* LISTEN 5913/glusterfsd > > > The other nodes logs fill up with errors because they can't reach the daemon anymore. They try to reach it on the "new" port instead of the old one: &...

...? ?Y ? ? ? 28777 ?Task Status of Volume public ------------------------------------------------------------------------------ There are no active volume tasks ??However the active process is STILL the same pid AND still listening on the old port ?root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster tcp ? ? ? ?0 ? ? ?0 0.0.0.0:49152 <http://0.0.0.0:49152> ? ? ? ? ? 0.0.0.0:* ? ? ? ? ? ? ? LISTEN ? ? ?5913/glusterfsd ??The other nodes logs fill up with errors because they can't reach the daemon anymore. They try to reach it on the "new" port instead of the old...

...------------------------------------------------------------------ >> There are no active volume tasks >> >> >> However the active process is STILL the same pid AND still listening on >> the old port >> >> root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster >> tcp 0 0 0.0.0.0:49152 0.0.0.0:* >> LISTEN 5913/glusterfsd >> >> >> The other nodes logs fill up with errors because they can't reach the >> daemon anymore. They try to reach it on the "new" port instead o...

...tarted out asking if you could have network browsing with a samba AD DC like there is with samba3, well the answer to this is 'no' I am not saying you shouldn't have kerberos installed, just the opposite in fact, you just cannot run the server part of it. Try running this: netstat -tapn | grep ':88' | grep 'samba' If you do not get a response, you have a big problem. Rowland

...? ?Y ? ? ? 28777 ?Task Status of Volume public ------------------------------------------------------------------------------ There are no active volume tasks ??However the active process is STILL the same pid AND still listening on the old port ?root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster tcp ? ? ? ?0 ? ? ?0 0.0.0.0:49152 <http://0.0.0.0:49152> ? ? ? ? ? 0.0.0.0:* ? ? ? ? ? ? ? LISTEN ? ? ?5913/glusterfsd ??The other nodes logs fill up with errors because they can't reach the daemon anymore. They try to reach it on the "new" port instead of the old...

...ublic > > ------------------------------------------------------------------------------ > There are no active volume tasks > > > However the active process is STILL the same pid AND still listening on > the old port > > root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster > tcp 0 0 0.0.0.0:49152 0.0.0.0:* > LISTEN 5913/glusterfsd > > > The other nodes logs fill up with errors because they can't reach the > daemon anymore. They try to reach it on the "new" port instead of the old > one: >...

Hi, Can''t get the rails demo to run. I''ve started the webrick server. Here is what the output looks like: ----- [root@chat demo]# ruby script/server => Booting WEBrick => Rails 2.3.3 application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server [2009-08-18 21:29:41] INFO WEBrick 1.3.1 [2009-08-18 21:29:41] INFO ruby 1.8.5

...me public > ------------------------------------------------------------------------------ > There are no active volume tasks > ? > ? > However the active process is STILL the same pid AND still listening on the old port > ? > root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster > tcp ? ? ? ?0 ? ? ?0 0.0.0.0:49152 ? ? ? ? ? 0.0.0.0:* ? ? ? ? ? ? ? LISTEN ? ? ?5913/glusterfsd > ? > ? > The other nodes logs fill up with errors because they can't reach the daemon anymore. They try to reach it on the "new" port instead of the old one: &...

...N/A N/A Y 28777 Task Status of Volume public ------------------------------------------------------------------------------ There are no active volume tasks However the active process is STILL the same pid AND still listening on the old port root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster tcp 0 0 0.0.0.0:49152 0.0.0.0:* LISTEN 5913/glusterfsd The other nodes logs fill up with errors because they can't reach the daemon anymore. They try to reach it on the "new" port instead of the old one: [2017-09-21 08:33:25.225006] E [socket.c:2327:socket_connect_fi...

...------ >>> ------------------ >>> There are no active volume tasks >>> >>> >>> However the active process is STILL the same pid AND still listening on >>> the old port >>> >>> root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster >>> tcp 0 0 0.0.0.0:49152 0.0.0.0:* >>> LISTEN 5913/glusterfsd >>> >>> >>> The other nodes logs fill up with errors because they can't reach the >>> daemon anymore. They try to reach it on the "...

...blic > ------------------------------------------------------------ > ------------------ > There are no active volume tasks > > > However the active process is STILL the same pid AND still listening on > the old port > > root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster > tcp 0 0 0.0.0.0:49152 0.0.0.0:* > LISTEN 5913/glusterfsd > > > The other nodes logs fill up with errors because they can't reach the > daemon anymore. They try to reach it on the "new" port instead of the old > one: >...

...---------- >>>> There are no active volume tasks >>>> >>>> >>>> However the active process is STILL the same pid AND still listening on >>>> the old port >>>> >>>> root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster >>>> tcp 0 0 0.0.0.0:49152 0.0.0.0:* >>>> LISTEN 5913/glusterfsd >>>> >>>> >>>> The other nodes logs fill up with errors because they can't reach the >>>> daemon anymore. They try t...

...? ?Y ? ? ? 28777 ?Task Status of Volume public ------------------------------------------------------------------------------ There are no active volume tasks ??However the active process is STILL the same pid AND still listening on the old port ?root at 192.168.140.43:/var/log/glusterfs# netstat -tapn | grep gluster tcp ? ? ? ?0 ? ? ?0 0.0.0.0:49152 <http://0.0.0.0:49152> ? ? ? ? ? 0.0.0.0:* ? ? ? ? ? ? ? LISTEN ? ? ?5913/glusterfsd ??The other nodes logs fill up with errors because they can't reach the daemon anymore. They try to reach it on the "new" port instead of the old...