AIX keeps it's errors in a binary file by default. Use errpt to look for errors. The typical netstat and telnet commands to make sure your network ports are not blocked/not listening. There is no AIX equivalent to SE Linux so no worries there. If it were a firewall it would not be intermittent...<br>
<br><div class="gmail_quote">On Fri, Apr 1, 2011 at 9:18 AM, chris fedde <span dir="ltr"><<a href="mailto:chris@fedde.us">chris@fedde.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Oh. and check the syslogs on the remote. But I'm sure you already did that.<br>
<div><div></div><div class="h5"><br>
On Fri, Apr 1, 2011 at 9:16 AM, chris fedde <<a href="mailto:chris@fedde.us">chris@fedde.us</a>> wrote:<br>
> Without more info all I can recommend is adding more instrumentation<br>
> and logging to the agent and checking the logs around failure.<br>
> Python includes a pretty powerful logging subsystem iirc.<br>
><br>
> Normal problem partitioning rules apply.<br>
><br>
> chris<br>
><br>
> On Fri, Apr 1, 2011 at 9:13 AM, Mike Bean <<a href="mailto:beandaemon@gmail.com">beandaemon@gmail.com</a>> wrote:<br>
>> Real briefly, and without going into anything confidential or getting bogged<br>
>> down in hoary details. We have a LX/UX agent written mostly in python,<br>
>> lives on the machines, gathers up certain data points into dbe files, and<br>
>> ships them off to a win2008 host for processing into a database.<br>
>> My problem is this, when the agent fails it isn't terribly descriptive, and<br>
>> the vast majority of our LX/UX failures are AIX. We don't get nearly the<br>
>> ticket volume in RHEL or SLES that we get in AIX/Solaris. Since apparently<br>
>> AIX requires PPC processors, I can't VM it and play around with it, and<br>
>> unfortunately, I don't have allot of experience with it, so troubleshooting<br>
>> these intermittent connection issues feels a bit like shooting in the dark.<br>
>> Strictly speaking, all we really need for a successfull connection is an<br>
>> open HTTP port. 26542.<br>
>> So what I need to focus on is any security/firewall elements of AIX that<br>
>> could shut us down - things like SE linux/firewalls...etc...etc...<br>
>> Ultimately, what I'm looking for is advice on how to effectively<br>
>> troubleshoot intermittent connection problems with AIX.<br>
>> Bean<br>
>><br>
>> On Fri, Apr 1, 2011 at 8:36 AM, Jim Ockers <<a href="mailto:ockers@ockers.net">ockers@ockers.net</a>> wrote:<br>
>>><br>
>>> Hi,<br>
>>><br>
>>> I agree with Chris that AIX is not a linux distro, but given that many<br>
>>> people on this list use some sort of unix (including linux) and/or are<br>
>>> interested in it, could you post your questions to the list? I'd be<br>
>>> interested to see what your questions/problems with AIX are.<br>
>>><br>
>>> I used AIX briefly a long time ago, IIRC one of the times was on an "Apple<br>
>>> Network Server" hardware. One command I remember was "smit" which was a<br>
>>> systems management tool.<br>
>>><br>
>>> Jim<br>
>>><br>
>>> --<br>
>>> Jim Ockers, P.Eng. (<a href="mailto:ockers@ockers.net">ockers@ockers.net</a>)<br>
>>> Contact info: <a href="http://www.ockers.net/msi.html" target="_blank">http://www.ockers.net/msi.html</a><br>
>>><br>
>>> chris fedde wrote:<br>
>>><br>
>>> AIX is not a "linux distro" it is derived from BSD with lots of cross<br>
>>> pollination from System V. But what are the questions and feel free<br>
>>> to mail me directly.<br>
>>><br>
>>> On Fri, Apr 1, 2011 at 8:22 AM, Mike Bean <<a href="mailto:beandaemon@gmail.com">beandaemon@gmail.com</a>> wrote:<br>
>>><br>
>>><br>
>>> Do we have anyone in CLUE who's experienced with AIX, wouldn't mind<br>
>>> fielding<br>
>>> a couple questions for me? Why on earth in this day and age people would<br>
>>> still be running proprietary linux distros is beyond me, but I'm having<br>
>>> some<br>
>>> work issues and I'd appreciate a sounding board who's more experienced<br>
>>> with<br>
>>> the distro, and wouldn't mind me pinging them with questions about it from<br>
>>> time to time.<br>
>>> thanks and regards,<br>
>>> Bean<br>
>>> _______________________________________________<br>
>>> clue mailing list<br>
>>> <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
>>> <a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> clue mailing list<br>
>>> <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
>>> <a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> clue mailing list<br>
>>> <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
>>> <a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> clue mailing list<br>
>> <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
>> <a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
>><br>
><br>
_______________________________________________<br>
clue mailing list<br>
<a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</div></div></blockquote></div><br>