is there a place to report bugs on V20 beta

[chrisjako]

just had event 30035 :

The following service(s) were interrupted: 3CXPhoneSystem01

It stopped my server from working

noone was doing anything at the time of shutdown

 

[SteveITS]

3CXPhoneSystemMC01?
https://www.3cx.com/community/threa...aily-interrupting-after-update-to-v20.123808/

 

[Alphabetic]

What did you do to resolve?

Can you tell me the spec of your CPU and RAM? Curious to know as i've seen another post with the same issue.

 

[Christopher_Jackson]

What did you do to resolve?

Can you tell me the spec of your CPU and RAM? Curious to know as i've seen another post with the same issue.

Its an on premise PBX dell server, so i logged into it and went to dashboard then services and started the stopped service, eveything was back online instantly and its been stable ever since.

Intel E5-2620 - 16 cores total
32GB RAM

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 16
On-line CPU(s) list: 0-15
Vendor ID: GenuineIntel
BIOS Vendor ID: Intel
Model name: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
BIOS Model name: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz CPU @ 2.1GHz
BIOS CPU family: 179
CPU family: 6
Model: 79
Thread(s) per core: 2
Core(s) per socket: 8
Socket(s): 1
Stepping: 1
CPU(s) scaling MHz: 43%
CPU max MHz: 3000.0000
CPU min MHz: 1200.0000
BogoMIPS: 4199.79
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perf
e3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3
ep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap intel_pt xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts md_clear flush_l1d
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 256 KiB (8 instances)
L1i: 256 KiB (8 instances)
L2: 2 MiB (8 instances)
L3: 20 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-15


# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x1000, DMI type 16, 23 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: Multi-bit ECC
Maximum Capacity: 3 TB
Error Information Handle: Not Provided
Number Of Devices: 24

Handle 0x1100, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 72 bits
Data Width: 64 bits
Size: 16 GB
Form Factor: DIMM
Set: 1
Locator: A1
Bank Locator: Not Specified
Type: DDR4
Type Detail: Synchronous Registered (Buffered)
Speed: 2133 MT/s
Manufacturer: 00CE00B300CE
Serial Number: 40691460
Asset Tag: 00152030
Part Number: M393A2G40DB0-CPB
Rank: 2
Configured Memory Speed: 2133 MT/s
Minimum Voltage: 1.2 V
Maximum Voltage: 1.2 V
Configured Voltage: 1.2 V

Handle 0x1101, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 72 bits
Data Width: 64 bits
Size: 16 GB
Form Factor: DIMM
Set: 1
Locator: A2
Bank Locator: Not Specified
Type: DDR4
Type Detail: Synchronous Registered (Buffered)
Speed: 2133 MT/s
Manufacturer: 00CE00B300CE
Serial Number: 4069244A
Asset Tag: 00152030
Part Number: M393A2G40DB0-CPB
Rank: 2
Configured Memory Speed: 2133 MT/s
Minimum Voltage: 1.2 V
Maximum Voltage: 1.2 V
Configured Voltage: 1.2 V

 

[SweetAction]

You will have to look at the logs to see why the service stopped. In debian it will be in the syslog, in Windows in the Event Viewer.

 

[TheodorosG_3CX]

As @SweetAction mentioned you need to check the syslog file for further information. You issue can be also related with the forum post. If you issue persists i would suggest to create a support ticket to further investigate.

 

[chrisjako]

As @SweetAction mentioned you need to check the syslog file for further information. You issue can be also related with the forum post. If you issue persists i would suggest to create a support ticket to further investigate.

Thanks, I purchased a support ticket from you for another issue and found your support to be extremley helpful - i learned a lot in the process too

 

[chrisjako]

here is what i have in syslog, according to my email notification logs, the service went down at 15:23 :

2023-12-06T15:05:01.722743+00:00 sbsj CRON[385247]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2023-12-06T15:15:01.731206+00:00 sbsj CRON[385428]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2023-12-06T15:17:01.738162+00:00 sbsj CRON[385457]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
2023-12-06T15:19:09.959745+00:00 sbsj kernel: [1237571.025144] traps: 3CXPhoneSystem[124544] general protection ip:559ad5f40432 sp:7fad20ff8530 error:0 in 3CXPhoneSystem[559ad5be7000+46b000]
2023-12-06T15:19:10.373435+00:00 sbsj systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=killed, status=11/SEGV
2023-12-06T15:19:10.376487+00:00 sbsj systemd[1]: 3CXPhoneSystem01.service: Failed with result 'signal'.
2023-12-06T15:19:10.376987+00:00 sbsj systemd[1]: 3CXPhoneSystem01.service: Consumed 12h 52min 47.423s CPU time.
2023-12-06T15:25:01.746475+00:00 sbsj CRON[386089]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2023-12-06T15:27:58.041243+00:00 sbsj dhclient[736]: DHCPREQUEST for 10.11.224.8 on enp3s0f0 to 10.11.231.254 port 67
2023-12-06T15:27:58.042254+00:00 sbsj dhclient[736]: DHCPACK of 10.11.224.8 from 10.11.231.254
2023-12-06T15:27:58.057392+00:00 sbsj dhclient[736]: bound to 10.11.224.8 -- renewal in 1575 seconds.
2023-12-06T15:30:55.691586+00:00 sbsj systemd[1]: Starting 3CXPhoneSystem01.service - 3CX PhoneSystem 01 SIP Server...
2023-12-06T15:30:57.047262+00:00 sbsj systemd[1]: Started 3CXPhoneSystem01.service - 3CX PhoneSystem 01 SIP Server.
2023-12-06T15:35:01.755123+00:00 sbsj CRON[386859]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2023-12-06T15:45:01.763699+00:00 sbsj CRON[386997]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)

 

[SweetAction]

Do you have any scheduled reports?

 

[Charles_3CX]

The entry below indicates the service has stopped

2023-12-06T15:19:10.373435+00:00 sbsj systemd[1]: 3CXPhoneSystem01.service: Main process exited, code=killed, status=11/SEGV

But to check why this was we would need to check some logs from various locations and can not check via the forum, so it will require a support ticket to be opened from your partial for us to request the required data to check.