SEGV version 2.0.0

[st...@sroskam.nl]

Hello all,

Today I tried updating to version 2.0.0 from the new github repo.

If I start sagan from the shell it is starting up OK, but as soon as it starts sagan as daemon with systemctl start sagan I get a failure (signal=SEGV).

If I revert to earlier versions in the old repo I can get commit c9c22a5ea0882b5954e8dba94dcbf533a75cd0c1 from 26-10 running, but commit 43cd81adafdf6686584d40e8d1bc64fb120ddba6 from 28-10 gives me the same SEGV message as the most recent version.

I'm wondering if someone has also encountered the same issue and knows a solution.

The OS I'm running on is OS 18.04LTS and I have the core dump attached to this message.

Best regards,

Stef

[Da Beave]

Hello Stef, 

I opened a new "issue" for this.   What you run it manually,  it doesn't fault? 

--
You received this message because you are subscribed to the Google Groups "sagan-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sagan-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sagan-users/b90c8c17-ae4a-408c-a06b-2788ad8948b2n%40googlegroups.com.

[st...@sroskam.nl]

Indeed, if I run it manually it doesn't fault. If you need more information, please let me know.

Best regards,

Stef

Op dinsdag 19 januari 2021 om 17:44:37 UTC+1 schreef Da Beave:

[Da Beave]

When you run it manually with the --dameon flag,  does it fault?   I might want to see how you're starting it via systemd.  thanks.

To view this discussion on the web visit https://groups.google.com/d/msgid/sagan-users/d24884c4-02d1-494f-b9f0-ae769488b520n%40googlegroups.com.

[st...@sroskam.nl]

I have tested a couple of items:

- Manual start: OK

- Manual start with the --daemon flag: SEGV

          PID: 22357 (SaganMain)

           UID: 0 (root)

           GID: 0 (root)

        Signal: 11 (SEGV)

     Timestamp: Tue 2021-01-19 19:53:45 CET (22s ago)

  Command Line: ./sagan --daemon

    Executable: /usr/local/bin/sagan

 Control Group: /user.slice/user-1001.slice/session-3.scope

          Unit: session-3.scope

         Slice: user-1001.slice

       Session: 3

     Owner UID: 1001 (development)

       Boot ID: 873fa2c0b27448d7b6c190410694371a

    Machine ID: 95a10db4525e4b5aa84927d80b7eea75

      Hostname: tsaganinfra01

       Storage: /var/lib/systemd/coredump/core.SaganMain.0.873fa2c0b27448d7b6c190410694371a.22357.1611082425000000.lz4

       Message: Process 22357 (SaganMain) of user 0 dumped core.

- Systemd: Same as manual with --daemon flag

To be sure I have correct test results I ditched my testserver and recreated the testserver with puppet, again exactly the same results.

Best regards,

Stef

Op dinsdag 19 januari 2021 om 18:04:33 UTC+1 schreef Da Beave:

[st...@sroskam.nl]

I now tried the same on my development environment for sagan with the latest build and there I got a more meaningful core dump:

Program terminated with signal SIGSEGV, Segmentation fault.

#0  Sagan_Log (type=type@entry=2, format=format@entry=0x5583b2d55518 "[%s, line %d] Unable to get LOCK on file. (%s)") at util.c:215

Will try to look into the issue in more detail.

Best regards,

Stef

Op dinsdag 19 januari 2021 om 19:58:17 UTC+1 schreef st...@sroskam.nl:

[st...@sroskam.nl]

I think I have found the issue, will prepare a pull request for this.

Best regards,

Stef

Op dinsdag 19 januari 2021 om 22:04:24 UTC+1 schreef st...@sroskam.nl: