So I did some more investigating today. Looks like the services.py script
is not getting the IP passed into the "trig" method of the CobblerSvc
class. I verified this by writing the value of REMOTE_ADDR to a file, and
consistantly found it to be "None" which is what was written to the log
file that the status action parses.

Anyone have a direction I should be looking? I am running version 2.2.1.

Thanks

-C

On Mon, May 14, 2012 at 8:24 AM, Corey Kovacs <corey.kov...@gmail.com>wrote:

> James, thanks but the logs themselves don't have the ip address in them
> either, just a "None" where the IP should be. I suspect it's choking on
> trying to parse the log but not handling the "None" since the parser
> expects an IP. I'll investigate further today. I'll try your suggestion
> nonetheless, so thanks again.
>
> -C
>
>
> On Sat, May 12, 2012 at 9:37 AM, James Cammarata <j...@sngx.net> wrote:
>
>> On Fri, May 11, 2012 at 8:07 AM, Corey Kovacs <corey.kov...@gmail.com>
>> wrote:
>> > my cobbler install (2.2.1) is having problems with the 'cobbler status'
>> > command.
>> >
>> > It appears that the log files that get parsed are not getting the ip
>> address
>> > set and when it's parsed, there is an exception. I don't have that
>> exception
>> > right now, but it chokes on that field being assigned "None" instead of
>> an
>> > address. This install was upgraded from a 2.0.10 base which already had
>> > system entries.
>> >
>> > Issuing the cobbler status command, only reveals the current/last
>> system to
>> > be built. It is when I run the code by hand which is used in the
>> > action_status.py file, that i get the exception. The cobbler status
>> command
>> > doesn't show an error other than only a single item being returned.
>> >
>> > Any ideas where to look? I tried to find the code that writes to the log
>> > file in question but no luck yet.
>> >
>> > I do not have a way to update the install right now so I need to work
>> with
>> > what I have.
>> >
>> > As always, any assistance is appreciated.
>>
>> Archive your logs in /var/log/cobbler/tasks. A while back (like 2009)
>> the time stamp format was changed, so the line parsing is thrown off.
>> _______________________________________________
>> cobbler mailing list
>> cobbler@lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/cobbler
>>
>
>
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler

Reply via email to