Task xymongen terminated by signal 6 🔗 link

Running xymon 4.3.12 on Solaris 10 x86.

I'm having some difficulty tracking down what it is I have misconfigured.

Running the following:
 ( . /usr/local/xymon/server/etc/xymonserver.cfg;
/usr/local/xymon/server/bin/xymongen --recentgifs
--subpagecolumns=2 --report --debug )

The last 10 lines are:

17466 2013-08-29 17:05:17 load_layout: -- got line '#    man-page.'
17466 2013-08-29 17:05:17 load_layout: -- got line '#'
17466 2013-08-29 17:05:17 load_layout: -- got line '# You need to define at
least the Xymon server itself here.'
17466 2013-08-29 17:05:17 load_layout: -- got line ''
17466 2013-08-29 17:05:17 load_layout: -- got line '130.11.50.48
owipm1.er.usgs.gov      # bbd http://owipm1.er.usgs.gov/';
17466 2013-08-29 17:05:17 init_host(owipm1.er.usgs.gov)
17466 2013-08-29 17:05:17 load_layout: -- got line '152.61.237.88
owipm1.cr.usgs.gov      #'
17466 2013-08-29 17:05:17 init_host(owipm1.cr.usgs.gov)
17466 2013-08-29 17:05:17 load_state()
Abort(coredump)


I can provide a stack trace on the core file if that would be helpful.

-- 
                                         -- David Boldt
                                            <user-945c7be1b8e4@xymon.invalid>


    "Careful. We don't want to learn from this."
    --Bill Watterson (1958 - ), "Calvin and Hobbes"

On 29-08-2013 23:29, Boldt, David wrote:

[snip]

Please do.

Thanks,
Henrik

Hello Henrik,

Thanks for your response.  After having posted I discovered that the latest
update was not in place, having been applied to the home directory for the
xymon account, which was not at the base directory for xymon. After
applying the update to the correct location, xymongen appear to be happy.


If it's not bad form to change the topic in a thread, I am currently
dealing with a different XYmon issue. The test "http" oscillates between
green and "DNS error" in an odd way. It will be red for about 5 minutes,
and green for about 5 seconds, as if the server is receiving two nearly
synchronized reports with different outcomes.

server/etc/tasks.cfg has this for xymonnet:

[xymonnet]
ENVFILE /usr/local/xymon/server/etc/xymonserver.cfg
 NEEDS xymond
CMD xymonnet --report --ping --checkresponse --concurrency=64 --no-ares
--dnslog=$XYMONSERVERLOGS/xymonnet-err.log
 LOGFILE $XYMONSERVERLOGS/xymonnet.log
INTERVAL 5m

Log files xymon.log net and xymonnet-err.log are empty. Omitting option
--no-ares makes no difference.

On Sat, Aug 31, 2013 at 1:45 AM, Henrik Størner <user-ce4a2c883f75@xymon.invalid> wrote:

-- 
                                         -- David Boldt
                                            <user-945c7be1b8e4@xymon.invalid>


    "Careful. We don't want to learn from this."
    --Bill Watterson (1958 - ), "Calvin and Hobbes"

On 03-09-2013 16:38, Boldt, David wrote:

It is :-(

Check the "Status message received from <IP>" line on the status page for both the red and the green status (you can find them in the historical status). This usually happens when you have to servers running the test - this line will tell you where the updates are coming from.


Regards,
Henrik