sipXcom 25.01.0-rc-002 Configuration Issue

[SipXcom Newbie]

Hi OnRelay Support,

Bare-metal reinstall: sipxecs-setup completes and the UI comes-up
however the "Features" menu has one entry only, Phonebooks.

sipXcom Newbie

[Ivar Plahte]

Note many of the features there are telephony service dependent, so make sure you enable those first.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/20260525175515.53b07929%40tel.co.uk.

[SipXcom Newbie]

Hi there Ivar, appreciate your quick reply.

Can you help with the menu navigation to enable telephony?

Given the manual says:

"It is not required to define the phone in order for that phone
to register to the system..

you only need the user ID and SIP password to register."

The *only* config made has been to create a single user.

Thanks.

[SipXcom Newbie]

Just unfamiliarity with the UI. Doh. I see it now. Thanks.

[SipXcom Newbie]

Selected *everything* under "Telephony Services" and applied.

Message in blue appeared "Changes applied successfully".

System > Servers > Single-Server-Showing-Status-Configured > Services

Lists the same 11 basic services as before (all status: Running).

EXPECTED:
- an extended list,
- evidence of more processes running,
- something listening on 5060.

[Support]

Hello, services show up in the UI as they are enabled and configured by CF engine, which may not be immediate.

You can also check service status by running ’service sipxecs status’ from the command line, alternatively 'systemctl status sipxecs’ for a bit more detail.

Individual service logs are found under /var/log/sipxpbx.

Port 5060 is held by the SIP registrar / sipxregistrar service.

[Support]

Sorry, meant systemctl status sipxNNN for more details about each service.

> To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/F8508EA2-8973-45CC-9E17-66E1FC399EE9%40onrelay.net.

[SipXcom Newbie]

# service sipxecs status
sipxacccode is stopped
sipxconfig ( pid 5013 ) is running and listening on port
sipxbridge is stopped
/etc/init.d/sipxcallback: line 115: status: command not found
sipxcdr is stopped
freeswitch is stopped
sipxivr is stopped
sipxlogwatcher ( pid 1729 ) is running
sipxpublisher is stopped
sipxrelay is stopped
sipxsqa is stopped
sipxpage is stopped
sipxproxy is stopped
sipxregistrar is stopped
sipxrest is stopped
sipxrls is stopped
sipxsaa is stopped
sipxsupervisor ( pid 1019 ) is running
sipxrecording is stopped

----- Original Message -----
Date: Mon, 25 May 2026 21:59:25 +0200
From: Support <sup...@onrelay.net>
To: SipXcom Newbie <sipxcom-text...@tel.co.uk>
Cc: sipxco...@googlegroups.com
Subject: Re: : [sipxcom-users] sipXcom 25.01.0-rc-002 Configuration Issue

Run:

service sipxecs status

Also doublecheck all services are actually enabled in your UI.

> On May 25, 2026, at 9:56 PM, SipXcom Newbie
> <sipxcom-text...@tel.co.uk> wrote:
>
> Thanks for your help.
>
> # systemctl --no-legend --no-pager list-units "sipx*"
> sipxlogwatcher.service loaded active running logwatcher
> sipxsupervisor.service loaded active running supervisor
>
> # systemctl -t service --no-legend --no-pager | grep sipx
> sipxlogwatcher.service loaded active running
> logwatcher sipxsupervisor.service loaded active
> running supervisor
>
> # systemctl status sipxecs
> * sipxecs.service - SYSV: sipxecs is a script used for control and
> query of the> Loaded: loaded (/etc/rc.d/init.d/sipxecs; generated)
> Active: inactive (dead)
> Docs: man:systemd-sysv-generator(8)
>
> # ls -l /var/log/sipxpbx
> total 33396
> -rw-r--r-- 1 sipx sipx 107 May 25 00:10 audit-cleanup.log
> drwx------ 2 sipx sipx 33 May 24 18:47 firewall
> -rw-r--r-- 1 sipx sipx 4148571 May 25 19:21 sipxagent.log
> -rw------- 1 sipx sipx 0 May 24 18:47 sipxconfig-audit.log
> -rw------- 1 sipx sipx 0 May 24 18:47 sipxconfig-ldap.log
> -rw------- 1 sipx sipx 28124069 May 25 20:49 sipxconfig.log
> -rw------- 1 sipx sipx 0 May 24 18:48 sipxlogwatcher.log
> -rw------- 1 sipx sipx 12910 May 25 19:20 sipxsecurity.log
> -rw-r--r-- 1 sipx sipx 609 May 25 19:20 snmpd.log
> -rw-r--r-- 1 sipx sipx 0 May 24 18:48 snmp-fix-process-cron.log
> -rw-r--r-- 1 sipx sipx 3295 May 25 19:20 snmptrapd.log
> #
>
> # host localhost
> localhost has address 127.0.0.1
>
> # systemctl status
> * host.domain
> State: running [Green]
> Units: 419 loaded (incl. loaded aliases)
> Jobs: 0 queued
> Failed: 0 units
> Since: Mon 2026-05-25 19:20:49 BST; 1h 32min ago
> systemd: 252-55.el9_7.9.rocky.0.1

> https://groups.google.com/d/msgid/sipxcom-users/20260525205637.0c50cb22%40tel.co.uk

[Support]

This tells us all the listed services are indeed enabled, but not starting up even to a point when they start producing their own log output.

So something is really wrong in the setup there, the combination of sipxagent.log and sipxconfig.log should have the answer.

A 'service sipxecs restart’ command combined with a tail -f /var/log/sipxpbx/*.log in a different terminal should give a quick clue.

> <SnapShot_2026_05_25_21_03_13.png><SnapShot_2026_05_25_21_04_35.png>

[SipXcom Newbie]

Combined tail log sent to OnRelay Support by email.

[Support]

As mentioned services are not starting here due to the php-fpm package not being included by default on the target RL9 server build.

php-fpm can be manually installed there using yum / dnf.

We have also added the php-fpm dependency explicitly to the sipxpbx RPM specification, which will be included in update 3 that we are just about to ship.

[SipXcom Newbie]

As OS install and sipxcom install completed with success status, was it a miss?


# dnf update
Last metadata expiration check: 2:08:40 ago on Tue 26 May 2026 05:37:39 BST.
Dependencies resolved.
Nothing to do.
Complete!

# dnf install php-fpm
Last metadata expiration check: 2:09:20 ago on Tue 26 May 2026 05:37:39 BST.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
php-fpm x86_64 8.0.30-5.el9_7 appstream 1.6 M
Installing dependencies:
nginx-filesystem noarch 2:1.20.1-24.el9_7.3.rocky.0.1 appstream 10 k
php-common x86_64 8.0.30-5.el9_7 appstream 667 k

Transaction Summary
================================================================================
Install 3 Packages

Total download size: 2.3 M
Installed size: 16 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): nginx-filesystem-1.20.1-24.el9_7.3.rocky 2.0 kB/s | 10 kB 00:05
(2/3): php-common-8.0.30-5.el9_7.x86_64.rpm 126 kB/s | 667 kB 00:05
(3/3): php-fpm-8.0.30-5.el9_7.x86_64.rpm 298 kB/s | 1.6 MB 00:05
--------------------------------------------------------------------------------
Total 217 kB/s | 2.3 MB 00:10
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : php-common-8.0.30-5.el9_7.x86_64 1/3
Running scriptlet: nginx-filesystem-2:1.20.1-24.el9_7.3.rocky.0.1.noarc 2/3
Installing : nginx-filesystem-2:1.20.1-24.el9_7.3.rocky.0.1.noarc 2/3
Installing : php-fpm-8.0.30-5.el9_7.x86_64 3/3
Running scriptlet: php-fpm-8.0.30-5.el9_7.x86_64 3/3
/sbin/ldconfig: /lib64/libbsoncxx.so._noabi is not a symbolic link

/sbin/ldconfig: /lib64/libmongocxx.so._noabi is not a symbolic link


Verifying : nginx-filesystem-2:1.20.1-24.el9_7.3.rocky.0.1.noarc 1/3
Verifying : php-common-8.0.30-5.el9_7.x86_64 2/3
Verifying : php-fpm-8.0.30-5.el9_7.x86_64 3/3

Installed:
nginx-filesystem-2:1.20.1-24.el9_7.3.rocky.0.1.noarch
php-common-8.0.30-5.el9_7.x86_64
php-fpm-8.0.30-5.el9_7.x86_64

Complete!

SipXcom Newbie

[Support]

It is just a difference between different Rocky Linux 9 builds, sometimes Linux implementations are e.g. ‘minimal’ to include only bare necessity library dependencies, and then some dependencies may not be captured by the sipx installation specifications.

And as sipxecs is deployed across a wider range of RL9 builds for e.g. AWS, Azure etc we capture these and can add such dependencies explicitly.

Currently the sipx install specs pull in approx. 580 such dependencies.

If you have other similar missing dependencies (you might), they will also show up in sipxagent.log, and we can easily add them to the install specs.

Thanks for catching!

[The Messenger]

Sure, must be a nightmare!

Now, after rebooting, the services are still not starting. What next
to check (or did it need the dependency for the DB to be built intact
in the first place)?

SipXcom Newbie

[Support]

Hello,

Note we only test on GCP here, whereas such OS platform dependencies are pretty straightforward to resolve and can be recovered manually also after an installation.

You may also want to generate server profiles and / or reboot to ensure everything is corrected configwise, since systemctl disabled said services per their missing dependency.

If a service is not starting due to a dependency systemctl status <servicename> will normally give you a clue. Otherwise the sipxagent.log or the individual service log file will show what is wrong.

Nightmares are rather mostly found in hard java compatibility breaks towards upgraded subsystems such as javax / jakarta, spring, jetty, tapestry, hibernate that require refactoring of working production quality legacy code, but all of those are fortunately behind us now.

[SipXcom Newbie]

In the UI, every telephony service is enabled but fail to start.

# service sipxecs status
sipxacccode is stopped

sipxconfig ( pid 12329 ) is running and listening on port

sipxbridge is stopped
/etc/init.d/sipxcallback: line 115: status: command not found
sipxcdr is stopped
freeswitch is stopped
sipxivr is stopped

sipxlogwatcher ( pid 13010 ) is running

sipxpublisher is stopped
sipxrelay is stopped
sipxsqa is stopped
sipxpage is stopped
sipxproxy is stopped
sipxregistrar is stopped
sipxrest is stopped
sipxrls is stopped
sipxsaa is stopped

sipxsupervisor ( pid 14995 ) is running
sipxrecording is stopped

# service sipxecs restart
Synchronizing state of disable-transparent-hugepages.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable disable-transparent-hugepages

...

# service sipxecs status
sipxacccode is stopped

sipxconfig ( pid 88126 ) is running and listening on port

sipxbridge is stopped
/etc/init.d/sipxcallback: line 115: status: command not found
sipxcdr is stopped
freeswitch is stopped
sipxivr is stopped

sipxlogwatcher ( pid 88841 ) is running

sipxpublisher is stopped
sipxrelay is stopped
sipxsqa is stopped
sipxpage is stopped
sipxproxy is stopped
sipxregistrar is stopped
sipxrest is stopped
sipxrls is stopped
sipxsaa is stopped

sipxsupervisor ( pid 14995 ) is running
sipxrecording is stopped

# ls -l /var/log/sipxpbx/*.log
-rw-r--r-- 1 sipx sipx 107 May 29 00:10 /var/log/sipxpbx/audit-cleanup.log
-rw-r--r-- 1 sipx sipx 30820 May 29 15:12 /var/log/sipxpbx/sipxagent.log
-rw------- 1 sipx sipx 0 May 29 00:00 /var/log/sipxpbx/sipxconfig-audit.log
-rw------- 1 sipx sipx 0 May 29 00:00 /var/log/sipxpbx/sipxconfig-ldap.log
-rw------- 1 sipx sipx 6191852 May 29 15:13 /var/log/sipxpbx/sipxconfig.log
-rw-r--r-- 1 sipx sipx 0 May 29 00:00 /var/log/sipxpbx/sipxlogwatcher.log
-rw------- 1 sipx sipx 0 May 29 00:00 /var/log/sipxpbx/sipxsecurity.log
-rw-r--r-- 1 sipx sipx 0 May 29 00:00 /var/log/sipxpbx/snmpd.log
-rw-r--r-- 1 sipx sipx 0 May 29 00:00 /var/log/sipxpbx/snmp-fix-process-cron.log
-rw-r--r-- 1 sipx sipx 4606 May 26 11:42 /var/log/sipxpbx/snmptrapd.log


# tail /var/log/sipxpbx/sipxconfig.log
...
"2026-05-29T14:11:26.540000Z":297:JAVA:DEBUG:f.q.d.n:main:00000000:SchemaManagementToolCoordinator:"No schema actions specified for contributor 'orm'"

"2026-05-29T14:11:26.969000Z":299:JAVA:DEBUG:f.q.d.n:main:00000000:core:"HHH000513: Unable to create the ReflectionOptimizer for [org.sipfoundry.sipxconfig.freeswitch.FreeswitchCondition]: cannot find a getter for [_org.sipfoundry.sipxconfig.freeswitch.FreeswitchExtension.conditionsBackref] on type [org.sipfoundry.sipxconfig.freeswitch.FreeswitchCondition]"

"2026-05-29T14:11:27.008000Z":300:JAVA:DEBUG:f.q.d.n:main:00000000:core:"HHH000513: Unable to create the ReflectionOptimizer for [org.sipfoundry.sipxconfig.dialplan.InternationalRule]: cannot find a getter for [_org.sipfoundry.sipxconfig.dialplan.DialPlan.rulesBackref] on type [org.sipfoundry.sipxconfig.dialplan.InternationalRule]"

2026-05-29 15:12:00.093:INFO :omd.cluster:cluster-ClusterId{value='6a199eb09d0dc99dd8dc5d32', description='null'}-f.q.d.n:27017: Monitor thread successfully connected to server with description ServerDescription{address=f.q.d.n:27017, type=REPLICA_SET_PRIMARY, cryptd=false, state=CONNECTED, ok=true, minWireVersion=0, maxWireVersion=27, maxDocumentSize=16777216, logicalSessionTimeoutMinutes=30, roundTripTimeNanos=20596643, minRoundTripTimeNanos=0, setName='sipxecs', canonicalAddress=f.q.d.n:27017, hosts=[f.q.d.n:27017], passives=[], arbiters=[], primary='f.q.d.n:27017', tagSet=TagSet{[]}, electionId=7fffffff0000000000000008, setVersion=2, topologyVersion=TopologyVersion{processId=6a1578fab7b0742662d8173d, counter=6}, lastWriteDate=Fri May 29 15:11:50 BST 2026, lastUpdateTimeNanos=271821512290301}

Per Tuesday, where to check? TIA.

[OnRelay Support]

Hello, sipxagent.log should indicate if you have another missing OS platform dependency when starting up the various sipx* services. 

[The Messenger]

Hello, re "missing OS platform dependency" :-

# grep -i depend /var/log/sipxpbx/sipxagent.log

# grep -i error /var/log/sipxpbx/sipxagent.log
error: None of the promised owners for '/var/sipxdata/cfdata/1' exist -- see INFO logs for more
error: None of the promised groups for '/var/sipxdata/cfdata/1' exist -- see INFO logs for more
error: Errors encountered when actuating files promise '/var/sipxdata/cfdata/1'
error: Could not read file '/var/sipxdata/cfdata/1/sipxconfig.properties.ui'. (fopen: No such file or directory)
error: Errors encountered when actuating insert_lines promise '/var/sipxdata/cfdata/1/sipxconfig.properties.ui'
error: Can't stat file '/var/sipxdata/cfdata/1/postgres-pwd.properties' on 'localhost' in files.copy_from promise
error: Errors encountered when actuating files promise '/etc/sipxpbx/postgres-pwd.properties'
error: Could not read file '/var/sipxdata/cfdata/1/log4j.properties.part'. (fopen: No such file or directory)
error: Errors encountered when actuating insert_lines promise '/var/sipxdata/cfdata/1/log4j.properties.part'
error: Could not read file '/var/sipxdata/cfdata/1/log4j-relay.properties.part'. (fopen: No such file or directory)
error: Errors encountered when actuating insert_lines promise '/var/sipxdata/cfdata/1/log4j-relay.properties.part
error: Failed to chdir into '/etc/xinetd.d'. (chdir: 'No such file or directory')
error: Can't stat file '/var/sipxdata/cfdata/1/server-chain.crt' on 'localhost' in files.copy_from promise
error: Errors encountered when actuating files promise '/etc/httpd/conf.d/ssl/server-chain.crt'
error: Can't stat file '/var/sipxdata/cfdata/1/ca-bundle.crt' on 'localhost' in files.copy_from promise
error: Errors encountered when actuating files promise '/etc/httpd/conf.d/ssl/ca-bundle.crt'
error: Method 'apache_config' failed in some repairs
error: None of the promised owners for '/var/sipxdata/cfdata/1' exist -- see INFO logs for more
error: None of the promised groups for '/var/sipxdata/cfdata/1' exist -- see INFO logs for more
error: Errors encountered when actuating files promise '/var/sipxdata/cfdata/1'
error: Could not read file '/var/sipxdata/cfdata/1/sipxconfig.properties.ui'. (fopen: No such file or directory)
error: Errors encountered when actuating insert_lines promise '/var/sipxdata/cfdata/1/sipxconfig.properties.ui'
error: Can't stat file '/var/sipxdata/cfdata/1/postgres-pwd.properties' on 'localhost' in files.copy_from promise
error: Errors encountered when actuating files promise '/etc/sipxpbx/postgres-pwd.properties'
error: Could not read file '/var/sipxdata/cfdata/1/log4j.properties.part'. (fopen: No such file or directory)
error: Errors encountered when actuating insert_lines promise '/var/sipxdata/cfdata/1/log4j.properties.part'
error: Could not read file '/var/sipxdata/cfdata/1/log4j-relay.properties.part'. (fopen: No such file or directory)
error: Errors encountered when actuating insert_lines promise '/var/sipxdata/cfdata/1/log4j-relay.properties.part'
error: Failed to chdir into '/etc/xinetd.d'. (chdir: 'No such file or directory')
error: Can't stat file '/var/sipxdata/cfdata/1/server-chain.crt' on 'localhost' in files.copy_from promise
error: Errors encountered when actuating files promise '/etc/httpd/conf.d/ssl/server-chain.crt'
error: Can't stat file '/var/sipxdata/cfdata/1/ca-bundle.crt' on 'localhost' in files.copy_from promise
error: Errors encountered when actuating files promise '/etc/httpd/conf.d/ssl/ca-bundle.crt'
error: Method 'apache_config' failed in some repairs

# grep sip /etc/passwd
sipx:x:983:983:sipx:/etc/sipxpbx:/bin/bash
PlcmSpIp:x:1002:1002::/var/sipxdata/configserver/phone/profile/tftproot:/sbin/nologin
lvp2890:x:1004:1004::/var/sipxdata/configserver/phone/profile/tftproot:/sbin/nologin

# grep sip /etc/group
sipx:x:983:

# cat INFO /var/log/sipxpbx/*.log | sed -ne '/owne/p' -e '/group/p'
info: Could not get GID for group '$(sipx.SIPXPBXGROUP)', (getgrnam: not found)
info: Could not get GID for group '$(sipx.SIPXPBXGROUP)', (getgrnam: not found)
error: None of the promised owners for '/var/sipxdata/cfdata/1' exist -- see INFO logs for more
error: None of the promised groups for '/var/sipxdata/cfdata/1' exist -- see INFO logs for more
info: Could not get GID for group '$(sipx.SIPXPBXGROUP)', (getgrnam: not found)
info: Could not get GID for group '$(sipx.SIPXPBXGROUP)', (getgrnam: not found)

# python3 /tmp/getgrnam_test.py
Group Name: sipx
Group ID (GID): 983
Group Members:

# grep -i fail /var/log/sipxpbx/sipxagent.log
info: Transforming '/var/sipxdata/tmp/security.conf.temp' with '/usr/libexec/sipXecs/sipx-config-maker --in /var/sipxdata/cfdata/1/security.yaml --out /var/sipxdata/tmp/security.conf.temp --template /etc/sipxpbx/fail2ban/security.erb'
info: Transformed '/var/sipxdata/tmp/security.conf.temp' with '/usr/libexec/sipXecs/sipx-config-maker --in /var/sipxdata/cfdata/1/security.yaml --out /var/sipxdata/tmp/security.conf.temp --template /etc/sipxpbx/fail2ban/security.erb'
info: Transformer '/var/sipxdata/tmp/security.conf.temp' => '/usr/libexec/sipXecs/sipx-config-maker --in /var/sipxdata/cfdata/1/security.yaml --out /var/sipxdata/tmp/security.conf.temp --template /etc/sipxpbx/fail2ban/security.erb' seemed to work ok
info: Transforming '/etc/sipxpbx/sipxlogwatcher.d/security.tmp' with '/usr/libexec/sipXecs/sipxlogwatcher-maker --in /var/sipxdata/cfdata/1/alarms.yaml --template /etc/sipxpbx/fail2ban/security.sec.erb --out /etc/sipxpbx/sipxlogwatcher.d/security.tmp'
info: Transformed '/etc/sipxpbx/sipxlogwatcher.d/security.tmp' with '/usr/libexec/sipXecs/sipxlogwatcher-maker --in /var/sipxdata/cfdata/1/alarms.yaml --template /etc/sipxpbx/fail2ban/security.sec.erb --out /etc/sipxpbx/sipxlogwatcher.d/security.tmp'
info: Transformer '/etc/sipxpbx/sipxlogwatcher.d/security.tmp' => '/usr/libexec/sipXecs/sipxlogwatcher-maker --in /var/sipxdata/cfdata/1/alarms.yaml --template /etc/sipxpbx/fail2ban/security.sec.erb --out /etc/sipxpbx/sipxlogwatcher.d/security.tmp' seemed to work ok
error: Failed to chdir into '/etc/xinetd.d'. (chdir: 'No such file or directory')
error: Method 'apache_config' failed in some repairs
info: Transforming '/var/sipxdata/tmp/security.conf.temp' with '/usr/libexec/sipXecs/sipx-config-maker --in /var/sipxdata/cfdata/1/security.yaml --out /var/sipxdata/tmp/security.conf.temp --template /etc/sipxpbx/fail2ban/security.erb'
info: Transformed '/var/sipxdata/tmp/security.conf.temp' with '/usr/libexec/sipXecs/sipx-config-maker --in /var/sipxdata/cfdata/1/security.yaml --out /var/sipxdata/tmp/security.conf.temp --template /etc/sipxpbx/fail2ban/security.erb'
info: Transformer '/var/sipxdata/tmp/security.conf.temp' => '/usr/libexec/sipXecs/sipx-config-maker --in /var/sipxdata/cfdata/1/security.yaml --out /var/sipxdata/tmp/security.conf.temp --template /etc/sipxpbx/fail2ban/security.erb' seemed to work ok
info: Transforming '/etc/sipxpbx/sipxlogwatcher.d/security.tmp' with '/usr/libexec/sipXecs/sipxlogwatcher-maker --in /var/sipxdata/cfdata/1/alarms.yaml --template /etc/sipxpbx/fail2ban/security.sec.erb --out /etc/sipxpbx/sipxlogwatcher.d/security.tmp'
info: Transformed '/etc/sipxpbx/sipxlogwatcher.d/security.tmp' with '/usr/libexec/sipXecs/sipxlogwatcher-maker --in /var/sipxdata/cfdata/1/alarms.yaml --template /etc/sipxpbx/fail2ban/security.sec.erb --out /etc/sipxpbx/sipxlogwatcher.d/security.tmp'
info: Transformer '/etc/sipxpbx/sipxlogwatcher.d/security.tmp' => '/usr/libexec/sipXecs/sipxlogwatcher-maker --in /var/sipxdata/cfdata/1/alarms.yaml --template /etc/sipxpbx/fail2ban/security.sec.erb --out /etc/sipxpbx/sipxlogwatcher.d/security.tmp' seemed to work ok
error: Failed to chdir into '/etc/xinetd.d'. (chdir: 'No such file or directory')
error: Method 'apache_config' failed in some repairs

#

[Support]

Hello,

All of the below are normal cf engine log entries early on in a startup sequence. CF engine can be confusing since it prints a lot of ‘errors’ that are not faults, but triggers for action items or some files etc it looks for it cannot find and simply ignores. Or it may describe a real fault without using the term ‘error’, but e.g ’notice’, such as your previous issue:
notice: Q: ".../systemctl rest": Failed to restart php-fpm.service: Unit php-fpm.service not found.

So these logs need to be read, not grep’ed, as tedious as that might be.

systemctl status sipxregistrar should also be a good starting point and give a strong indication as to why that particular service is not starting. Same for the other sipx* services.

As mentioned before the below stopped services were previously disabled per the missing php dependency. So to recover from that you may need to do any of restarting sipxecs, reboot, regenerate server profiles, disable and reenable each service in the UI, and / or reinstall.

[Ivar Plahte]

I think a good rule of thumb is, if something fundamentally breaks or goes awry during an install, e.g. on a new HW platform/cloud image/OS build, after the root cause is understood and worked around or fixed, just go back to start and do it again. It takes 10min, whereas manually repairing a broken or incomplete sipxecs installation can be quite difficult and time consuming even for experienced sipxecs engineers.

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/CAK2_jwa1oe%3D3ZxahkeNSL62SxJG4RKCE6-97A4Ky17DAwfsc9g%40mail.gmail.com.

[Donkiss Boss]

Licensed Pharmaceuticals And Psychedelics Online Store
Buy the best Pharmaceuticals And Psychedelics products in our website with safe and guaranteed shipping and delivery Worldwide
Check out our website below if interested in our products.
https://shorturl.at/BvDVf
https://shorturl.at/ITBJW
https://shorturl.at/wCGS4
https://shorturl.at/RnP0b
https://shorturl.at/GTr8Q