ASL 2.0 Beta 3 on VMware ESXi 6.5 - segfault

I downloaded the ASL 2.0 Beta 3 ISO image and created a new virtual machine in VMware. I ran through the standard configuration process and started the processes as usual.

The asterisk.service is running but I see the following segfault in /var/log/syslog repeatedly every few seconds:
Feb 15 02:01:56 allstar systemd[1]: Created slice User Slice of UID 1000.
Feb 15 02:01:56 allstar systemd[1]: Starting User Runtime Directory /run/user/1000…
Feb 15 02:01:56 allstar systemd[1]: Started User Runtime Directory /run/user/1000.
Feb 15 02:01:56 allstar systemd[1]: Starting User Manager for UID 1000…
Feb 15 02:01:56 allstar systemd[564]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 15 02:01:56 allstar systemd[564]: Reached target Paths.
Feb 15 02:01:56 allstar systemd[564]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browse
rs).
Feb 15 02:01:56 allstar systemd[564]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 15 02:01:56 allstar systemd[564]: Listening on GnuPG network certificate management daemon.
Feb 15 02:01:56 allstar systemd[564]: Reached target Timers.
Feb 15 02:01:56 allstar systemd[564]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 15 02:01:56 allstar systemd[564]: Reached target Sockets.
Feb 15 02:01:56 allstar systemd[564]: Reached target Basic System.
Feb 15 02:01:56 allstar systemd[1]: Started User Manager for UID 1000.
Feb 15 02:01:56 allstar systemd[1]: Started Session 1 of user repeater.
Feb 15 02:01:56 allstar systemd[564]: Reached target Default.
Feb 15 02:01:56 allstar systemd[564]: Startup finished in 26ms.
Feb 15 02:02:12 allstar systemd[1]: Started Session 3 of user repeater.
Feb 15 02:02:26 allstar kernel: [ 35.468348] asterisk[598]: segfault at 191 ip 00007faf9707d118 sp 00007faf948e62a0 er
ror 4 in app_rpt.so[7faf97070000+39000]
Feb 15 02:02:26 allstar kernel: [ 35.468353] Code: 3e 3d ff ff 48 8d 54 24 18 be 02 00 20 00 48 89 df 31 c0 e8 fa 36 f
f ff 48 89 df e8 e2 30 ff ff e8 fd 32 ff ff 48 8b 44 24 18 <81> 38 c8 00 00 00 74 40 4c 8d 05 9a 14 03 00 48 8d 0d 2a 48
03 00
Feb 15 02:02:27 allstar kernel: [ 35.659411] asterisk[600]: segfault at 191 ip 00007faf9707d118 sp 00007faf948e62a0 er
ror 4 in app_rpt.so[7faf97070000+39000]
Feb 15 02:02:27 allstar kernel: [ 35.659416] Code: 3e 3d ff ff 48 8d 54 24 18 be 02 00 20 00 48 89 df 31 c0 e8 fa 36 f
f ff 48 89 df e8 e2 30 ff ff e8 fd 32 ff ff 48 8b 44 24 18 <81> 38 c8 00 00 00 74 40 4c 8d 05 9a 14 03 00 48 8d 0d 2a 48
03 00
Feb 15 02:02:58 allstar kernel: [ 67.596811] asterisk[604]: segfault at 191 ip 00007faf9707d118 sp 00007faf948e62a0 er
ror 4 in app_rpt.so[7faf97070000+39000]
Feb 15 02:02:58 allstar kernel: [ 67.596816] Code: 3e 3d ff ff 48 8d 54 24 18 be 02 00 20 00 48 89 df 31 c0 e8 fa 36 f
f ff 48 89 df e8 e2 30 ff ff e8 fd 32 ff ff 48 8b 44 24 18 <81> 38 c8 00 00 00 74 40 4c 8d 05 9a 14 03 00 48 8d 0d 2a 48
03 00
Feb 15 02:02:59 allstar kernel: [ 67.787430] asterisk[606]: segfault at 191 ip 00007faf9707d118 sp 00007faf948e62a0 er
ror 4 in app_rpt.so[7faf97070000+39000]
Feb 15 02:02:59 allstar kernel: [ 67.787435] Code: 3e 3d ff ff 48 8d 54 24 18 be 02 00 20 00 48 89 df 31 c0 e8 fa 36 f
f ff 48 89 df e8 e2 30 ff ff e8 fd 32 ff ff 48 8b 44 24 18 <81> 38 c8 00 00 00 74 40 4c 8d 05 9a 14 03 00 48 8d 0d 2a 48
03 00

I thought perhaps there might have been an issue with not having open-vm-tools installed, but I added them and rebooted and am still seeing the same message.

Is this a known issue? Is there any additional diagnostic information you would like to see before I do anything else with the VM?

-JeffH

I’ve seen this too on my VM. It’s a documented issue and we’ll be releasing a fix for it in the near future. The segfault doesn’t seem to cause any problems but it’s obviously very noisy :slight_smile:

Cheers,
Rob

OK - good deal. As long as you’re aware of it. That’s most important. I haven’t noticed that it created any issues. The service just keeps humming along.

Thanks!

I’ve played a little with running the 2.0 beta under VirtualBox (host is Win10) and it seems quite happy to do so