Re: ARS 7.5p007 on SLES11
Hi, Not on SUSE but RH. What I would do is comment out (using #) the arserverd line from the armonitor.conf Then from the shell, set LD_LIBRARY_PATH to the bin and lib directory of your installation. Then run the whole line from the armonitor.conf that has arserverd. Any issues will be printed to the screen. It will most likely be missing certain links etc The issue is that sometimes what is called standard out (stdio) gets swallowed up by the armonitor process. Kind regards Danny Single Sign On (SSO) for BMC Remedy AR System and ITSM. http://www.javasystemsolutions.com/jss/ssoplugin -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of michep Sent: 04 March 2011 11:34 To: arslist@ARSLIST.ORG Subject: ARS 7.5p007 on SLES11 Hello listers. Is here anyone who have real experience of installing ARS75 server on SUSE11? I stuck in a problem - arserver cant register itself in portmapper. Starting arsystem prints AR System Server unable to create (390600, 0) for TCP. ARMonitor child process (pid:17889) died with 256. ./arserverd and unable to create (390695, 0) for TCP ARMonitor child process (pid:17888) died with 256. ./arplugin And yes, rpcbind service is up and running. If I switch to fixed TCP ports without portmapping - everything is fine. Any comments? ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
Hello Conny. Thanx for reply. Yes, you know, I found something strange in /etc/hosts: 127.0.0.1 msk-m1-rem001.x5.ru localhost 127.0.0.2 msk-m1-rem001.x5.ru msk-m1-rem001 192.168.65.199 msk-m1-rem001.x5.ru msk-m1-rem001 I fixed it to: 127.0.0.1 localhost #127.0.0.2 msk-m1-rem001.x5.ru msk-m1-rem001 192.168.65.199 msk-m1-rem001.x5.ru msk-m1-rem001 but it does not help. Still the same errors on startup with portmapper registering enabled. On 4 мар, 22:13, Conny Martin wrote: > I installed a AR-Server 7.5 on Opensuse 11 and afaik this is the base for the > sles versions. I had the same problem. In my case the problem was localhost > pointing to 127.0.0.2 instead of 127.0.1 Portmapper is accepting registration > requests only from "local" adresses and treated 127.0.0.2 not as a local > adress. > > So have a look at your /etc/hosts file and check which ip address is mapped > to localhost. > > HTH ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
Hello Danny. I did "clean" startup of arserverd - unset LD_LIBRARY_PATH and tries several times to see whitch libraries is required to run. Finally it was started with LD_LIBRARY_PATH=/opt/bmc/ARSystem/bin:/lib:/usr/lib:/opt/oracle/ product/11gR1/client/lib but does not see any additional information, only the same error: AR System Server unable to create (390600, 0) for TCP On 4 мар, 14:58, Danny Kellett wrote: > What I would do is comment out (using #) the arserverd line from the > armonitor.conf > > Then from the shell, set LD_LIBRARY_PATH to the bin and lib directory of > your installation. > Then run the whole line from the armonitor.conf that has arserverd. > > Any issues will be printed to the screen. It will most likely be missing > certain links etc The issue is that sometimes what is called standard out > (stdio) gets swallowed up by the armonitor process. > > Kind regards > Danny ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
Then how about setting portmapper to f and tcd port to a number? Sent from my iPhone On 5 Mar 2011, at 10:03, michep wrote: > Hello Danny. > > I did "clean" startup of arserverd - unset LD_LIBRARY_PATH and tries > several times to see whitch libraries is required to run. Finally it > was started with > > LD_LIBRARY_PATH=/opt/bmc/ARSystem/bin:/lib:/usr/lib:/opt/oracle/ > product/11gR1/client/lib > > but does not see any additional information, only the same error: > > AR System Server unable to create (390600, 0) for TCP > > > On 4 мар, 14:58, Danny Kellett > wrote: >> What I would do is comment out (using #) the arserverd line from the >> armonitor.conf >> >> Then from the shell, set LD_LIBRARY_PATH to the bin and lib directory of >> your installation. >> Then run the whole line from the armonitor.conf that has arserverd. >> >> Any issues will be printed to the screen. It will most likely be missing >> certain links etc The issue is that sometimes what is called standard out >> (stdio) gets swallowed up by the armonitor process. >> >> Kind regards >> Danny > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
Danny, my server was installed without portmapper and with fixed TCP ports. Config was something like that: Register-With-Portmapper:F TCD-Specific-Port: 35000 Plugin-Port: 36000 and with this config server is starting just fine. But I need portmapper ... On 5 мар, 16:55, Danny Kellett wrote: > Then how about setting portmapper to f and tcd port to a number? ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
Try starting rpcbind in debug mode to see what it reports. Look in /var/log/messages to see if rpcbind is reporting anything there already. On Sat, Mar 5, 2011 at 2:35 PM, michep wrote: > Danny, > > my server was installed without portmapper and with fixed TCP ports. > Config was something like that: > > Register-With-Portmapper:F > TCD-Specific-Port: 35000 > Plugin-Port: 36000 > > and with this config server is starting just fine. But I need > portmapper ... > > On 5 мар, 16:55, Danny Kellett > wrote: > > Then how about setting portmapper to f and tcd port to a number? > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" > ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
OMG! Its getting more and more interesting with every step!
Ok, thanx to Conny ("-i" parameter to rpcbind service) now im able to
start ARS server with Register-With-Portmapper:T option without
errors. BUT!!!
Now trying to connect to ARS server with RUT without specified TCP
port I receive error:
ARERR [90] Cannot establish a network connection to the AR System
server : msk-m1-rem001 : RPC: Miscellaneous tli error - System error
(Connection refused)
Ok, thanx to Axton, I stop rpcbind service and started it in debug
mode: rpcbind -id, and able to see whats happen inside.
Restart ARS server, and see that a lot of registration commands
(RPCB_SET) was processed and succeeded.
Now, connecting with RUT without specified TCP and see rpc command in
rpcbind log:
PMAP_GETPORT req for (390620, 18, tcp) from
192.168.170.10.250.247 :port = 47240
So, comment was proessed and port number was returned - 47240.
WTH!? I didn't remove port options in ar.conf, now its looks like:
Register-With-Portmapper: T
TCD-Specific-Port: 35000
Plugin-Port: 36000
and netstat shows that ports 35000 and 36000 are in LISTEN state, so
why rpcbind returned wrong port number?
Next, comment out port options:
Register-With-Portmapper: T
#TCD-Specific-Port: 35000
#Plugin-Port: 36000
and restart ARS server, truing to connect with RUT without specified
TCP port - error again, rpcbind returns:
PMAP_GETPORT req for (390620, 18, tcp) from
192.168.170.10.223.199 :port = 18773
BUT! ARS server is listening on different port:
# lsof +M -p 13564|grep IPv4
...
arserverd 13564 root9u IPv4 1994493 0t0 TCP *:21833
(LISTEN)
...
Whats goning on?!
And even one more finding - in this configuration arplugin reports
segfault every one and a half minutes:
Mar 9 16:02:10 msk-m1-rem001 kernel: [2598443.587831]
arplugin[13909]: segfault at 1c ip f6a33cc1 sp
f42fae28 error 4 in libc-2.11.1.so[f69c2000+15b000]
I call support ...
On 6 мар, 12:48, Conny Martin wrote:
> so go to /etc/sysconfig/rpcbind and add this line
>
> RPCBIND_OPTIONS="-i"
>
> then restart rpcbind (/etc/init.d/rpcbind restart)
> you should now see the -i option in ps output
> If you start your arserver it should now be able to register with portmapper
On 6 мар, 02:33, Axton wrote:
> Try starting rpcbind in debug mode to see what it reports. Look in
> /var/log/messages to see if rpcbind is reporting anything there already.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
Use rpcinfo to look at the rpc program/port registration. The output should
look something like this:
agrams@phx-remarsiso-01 agrams$ rpcinfo -p
program vers proto port service
104 tcp111 rpcbind
103 tcp111 rpcbind
102 tcp111 rpcbind
104 udp111 rpcbind
103 udp111 rpcbind
102 udp111 rpcbind
...
3906008 tcp 2020 arserverd
3906009 tcp 2020 arserverd
390600 10 tcp 2020 arserverd
390600 11 tcp 2020 arserverd
390600 12 tcp 2020 arserverd
390600 13 tcp 2020 arserverd
390600 14 tcp 2020 arserverd
3906018 tcp 2020 arserverd
3906019 tcp 2020 arserverd
390601 10 tcp 2020 arserverd
390601 11 tcp 2020 arserverd
390601 12 tcp 2020 arserverd
390601 13 tcp 2020 arserverd
390601 14 tcp 2020 arserverd
...
Make sure the port matches what you have your arserver configured for. If
it doesn't then there is an issue with the RPC program registration. Look
back at the rpc debug logs for the RPCB_SET entries and see what those log
entries show. Do they show the right port?
If that doesn't reveal anything, get a packet dump (tcpdump) during your
attempt to login and use Wireshark to look for the rpcbind packets (tcp/111
and udp/111) and see what the communications contain. Wireshark will decode
the packets so that you can see the request and response in human readable
format.
Axton Grams
The opinions, statements, and/or suggested courses of action expressed in
this E-mail do not necessarily reflect those of BMC Software, Inc. My
voluntary participation in this forum is not intended to convey a role as a
spokesperson, liaison or public relations representative for BMC Software,
Inc.
2011/3/9 michep
> OMG! Its getting more and more interesting with every step!
>
> Ok, thanx to Conny ("-i" parameter to rpcbind service) now im able to
> start ARS server with Register-With-Portmapper:T option without
> errors. BUT!!!
> Now trying to connect to ARS server with RUT without specified TCP
> port I receive error:
>
> ARERR [90] Cannot establish a network connection to the AR System
> server : msk-m1-rem001 : RPC: Miscellaneous tli error - System error
> (Connection refused)
>
> Ok, thanx to Axton, I stop rpcbind service and started it in debug
> mode: rpcbind -id, and able to see whats happen inside.
>
> Restart ARS server, and see that a lot of registration commands
> (RPCB_SET) was processed and succeeded.
>
> Now, connecting with RUT without specified TCP and see rpc command in
> rpcbind log:
>
> PMAP_GETPORT req for (390620, 18, tcp) from
> 192.168.170.10.250.247 :port = 47240
>
> So, comment was proessed and port number was returned - 47240.
>
> WTH!? I didn't remove port options in ar.conf, now its looks like:
>
> Register-With-Portmapper: T
> TCD-Specific-Port: 35000
> Plugin-Port: 36000
>
> and netstat shows that ports 35000 and 36000 are in LISTEN state, so
> why rpcbind returned wrong port number?
>
> Next, comment out port options:
>
> Register-With-Portmapper: T
> #TCD-Specific-Port: 35000
> #Plugin-Port: 36000
>
> and restart ARS server, truing to connect with RUT without specified
> TCP port - error again, rpcbind returns:
>
> PMAP_GETPORT req for (390620, 18, tcp) from
> 192.168.170.10.223.199 :port = 18773
>
> BUT! ARS server is listening on different port:
>
> # lsof +M -p 13564|grep IPv4
> ...
> arserverd 13564 root9u IPv4 1994493 0t0 TCP *:21833
> (LISTEN)
> ...
>
> Whats goning on?!
>
> And even one more finding - in this configuration arplugin reports
> segfault every one and a half minutes:
>
> Mar 9 16:02:10 msk-m1-rem001 kernel: [2598443.587831]
> arplugin[13909]: segfault at 1c ip f6a33cc1 sp
> f42fae28 error 4 in libc-2.11.1.so[f69c2000+15b000]
>
> I call support ...
>
> On 6 мар, 12:48, Conny Martin wrote:
> > so go to /etc/sysconfig/rpcbind and add this line
> >
> > RPCBIND_OPTIONS="-i"
> >
> > then restart rpcbind (/etc/init.d/rpcbind restart)
> > you should now see the -i option in ps output
> > If you start your arserver it should now be able to register with
> portmapper
>
>
> On 6 мар, 02:33, Axton wrote:
> > Try starting rpcbind in debug mode to see what it reports. Look in
> > /var/log/messages to see if rpcbind is reporting anything there already.
>
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
>
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
Offhand question ... Did the ARS rpc info get added to the /etc/rpc file? If
you cat the file you should see the ARS ports 390600 thru 390695 (yes some
numbers are skipped).
Also you want the Plugin-Port in the ar.conf (as that is how the arsystemd
process communicates with the arplugin process).
Fred
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of michep
Sent: Wednesday, March 09, 2011 7:25 AM
To: arslist@ARSLIST.ORG
Subject: Re: ARS 7.5p007 on SLES11
OMG! Its getting more and more interesting with every step!
Ok, thanx to Conny ("-i" parameter to rpcbind service) now im able to
start ARS server with Register-With-Portmapper:T option without
errors. BUT!!!
Now trying to connect to ARS server with RUT without specified TCP
port I receive error:
ARERR [90] Cannot establish a network connection to the AR System
server : msk-m1-rem001 : RPC: Miscellaneous tli error - System error
(Connection refused)
Ok, thanx to Axton, I stop rpcbind service and started it in debug
mode: rpcbind -id, and able to see whats happen inside.
Restart ARS server, and see that a lot of registration commands
(RPCB_SET) was processed and succeeded.
Now, connecting with RUT without specified TCP and see rpc command in
rpcbind log:
PMAP_GETPORT req for (390620, 18, tcp) from
192.168.170.10.250.247 :port = 47240
So, comment was proessed and port number was returned - 47240.
WTH!? I didn't remove port options in ar.conf, now its looks like:
Register-With-Portmapper: T
TCD-Specific-Port: 35000
Plugin-Port: 36000
and netstat shows that ports 35000 and 36000 are in LISTEN state, so
why rpcbind returned wrong port number?
Next, comment out port options:
Register-With-Portmapper: T
#TCD-Specific-Port: 35000
#Plugin-Port: 36000
and restart ARS server, truing to connect with RUT without specified
TCP port - error again, rpcbind returns:
PMAP_GETPORT req for (390620, 18, tcp) from
192.168.170.10.223.199 :port = 18773
BUT! ARS server is listening on different port:
# lsof +M -p 13564|grep IPv4
...
arserverd 13564 root9u IPv4 1994493 0t0 TCP *:21833
(LISTEN)
...
Whats goning on?!
And even one more finding - in this configuration arplugin reports
segfault every one and a half minutes:
Mar 9 16:02:10 msk-m1-rem001 kernel: [2598443.587831]
arplugin[13909]: segfault at 1c ip f6a33cc1 sp
f42fae28 error 4 in libc-2.11.1.so[f69c2000+15b000]
I call support ...
On 6 мар, 12:48, Conny Martin wrote:
> so go to /etc/sysconfig/rpcbind and add this line
>
> RPCBIND_OPTIONS="-i"
>
> then restart rpcbind (/etc/init.d/rpcbind restart)
> you should now see the -i option in ps output
> If you start your arserver it should now be able to register with portmapper
On 6 мар, 02:33, Axton wrote:
> Try starting rpcbind in debug mode to see what it reports. Look in
> /var/log/messages to see if rpcbind is reporting anything there already.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
Frederick, both - altered /etc/rpc file and Plugin-Port option in ar.conf - are already in place, thanx. On 9 мар, 19:10, "Grooms, Frederick W" wrote: > Offhand question ... Did the ARS rpc info get added to the /etc/rpc file? If > you cat the file you should see the ARS ports 390600 thru 390695 (yes some > numbers are skipped). > Also you want the Plugin-Port in the ar.conf (as that is how the arsystemd > process communicates with the arplugin process). ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: ARS 7.5p007 on SLES11
Conny,
you just saying that problem is in rpcbind? And this package is in
public domain repository? Do you intent to connect with developers to
make patch?
And last question - can I get patched rpcbind binary, please?
On 10 мар, 12:22, Conny Martin wrote:
> Yes indeed, there is something strange.
>
> I've got the same issue. But I never realized the problem because I always
> connect to arsystem using a tcp port regardless of the
> "Register-With-Portmapper" setting.
>
> I digged through the sourcecode of rpcbind and found the problem. If a
> process is trying to register with portmapper the ip and port information is
> carried in a string. If the process trys to register a programm with tcpport
> 3334 the string is "0.0.0.0.6.13"
>
> 0.0.0.0 is for the ip address
> 6.13 is for the port
>
> 13 -> 0x0d
> 6 -> 0x06
> 0x0d06 -> 3334
>
> The algo for computing the port from this string swapped the two bytes and
> this leads to registering the wrong port.
>
> #ifdef PORTMAP
> /*
> * Extract port from universal TCP/UDP address
> */
> int
> uaddr2port(char *uaddr, u_long *p_port)
> {
> char *pt1, *pt2;
> int rc = -1;
>
> if ((pt1 = strrchr(uaddr, '.')) != NULL) {
> *pt1++ = 0;
> if ((pt2 = strrchr(uaddr, '.')) != NULL) {
> *pt2++ = 0;
> *p_port = atoi(pt1) * 256 + atoi(pt2); //Here I
> exchanged pt1 with pt2 and everything is working
> rc = 0;
> *--pt2 = '.';
> }
> *--pt1 = '.';
> }
> return rc;
>
> }
>
> Kind Regards Conny
>
> -----Ursprüngliche Nachricht-
> Von: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] Im Auftrag von michep
> Gesendet: Mittwoch, 9. März 2011 14:25
> An: arsl...@arslist.org
> Betreff: Re: ARS 7.5p007 on SLES11
>
> OMG! Its getting more and more interesting with every step!
>
> Ok, thanx to Conny ("-i" parameter to rpcbind service) now im able to start
> ARS server with Register-With-Portmapper:T option without errors. BUT!!!
> Now trying to connect to ARS server with RUT without specified TCP port I
> receive error:
>
> ARERR [90] Cannot establish a network connection to the AR System server :
> msk-m1-rem001 : RPC: Miscellaneous tli error - System error (Connection
> refused)
>
> Ok, thanx to Axton, I stop rpcbind service and started it in debug
> mode: rpcbind -id, and able to see whats happen inside.
>
> Restart ARS server, and see that a lot of registration commands
> (RPCB_SET) was processed and succeeded.
>
> Now, connecting with RUT without specified TCP and see rpc command in rpcbind
> log:
>
> PMAP_GETPORT req for (390620, 18, tcp) from
> 192.168.170.10.250.247 :port = 47240
>
> So, comment was proessed and port number was returned - 47240.
>
> WTH!? I didn't remove port options in ar.conf, now its looks like:
>
> Register-With-Portmapper: T
> TCD-Specific-Port: 35000
> Plugin-Port: 36000
>
> and netstat shows that ports 35000 and 36000 are in LISTEN state, so why
> rpcbind returned wrong port number?
>
> Next, comment out port options:
>
> Register-With-Portmapper: T
> #TCD-Specific-Port: 35000
> #Plugin-Port: 36000
>
> and restart ARS server, truing to connect with RUT without specified TCP port
> - error again, rpcbind returns:
>
> PMAP_GETPORT req for (390620, 18, tcp) from
> 192.168.170.10.223.199 :port = 18773
>
> BUT! ARS server is listening on different port:
>
> # lsof +M -p 13564|grep IPv4
> ...
> arserverd 13564 root 9u IPv4 1994493 0t0 TCP *:21833
> (LISTEN)
> ...
>
> Whats goning on?!
>
> And even one more finding - in this configuration arplugin reports segfault
> every one and a half minutes:
>
> Mar 9 16:02:10 msk-m1-rem001 kernel: [2598443.587831]
> arplugin[13909]: segfault at 1c ip f6a33cc1 sp
> f42fae28 error 4 in libc-2.11.1.so[f69c2000+15b000]
>
> I call support ...
>
> On 6 мар, 12:48, Conny Martin wrote:
>
> > so go to /etc/sysconfig/rpcbind and add this line
>
> > RPCBIND_OPTIONS="-i"
>
> > then restart rpcbind (/etc/init.d/rpcbind restart) you should now see
> > the -i option in ps output If you start your arserver it should now be
> > able to register with portmapper
>
> On 6 мар, 02:33, Axton wrote:
>
> > Try starting rpcbind in debug mode to see what it reports. Look in
> > /var/log/messages to see if rpcbind is reporting anything there already.
>
> ___
> UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgattend
> wwrug11www.wwrug.comARSList: "Where the Answers Are"
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
