From cappellari at connectlife.it Wed Jan 8 03:43:19 2025 From: cappellari at connectlife.it (Danny Cappellari) Date: Wed, 8 Jan 2025 08:43:19 +0000 (UTC) Subject: [Spce-user] BUG in ngcp-templates-ce 12.3.1.94 mr12.3.1.94 Message-ID: <435470833.899008.1736325799589.JavaMail.zextras@connectlife.it> Hello, we report a bug on the latest version ngcp-templates-ce 12.3.1.94 mr12.3.1.94 Updating to this version of templates causes kamailio-proxy to stop after executing the command ngcpcfg apply 'example' because the fifo file on /var/run/kamailio/kamailio.proxy.fifo is missing The environment where the error was detected is SIPWISE 12.3.1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cappellari at connectlife.it Fri Jan 10 04:36:30 2025 From: cappellari at connectlife.it (Danny Cappellari) Date: Fri, 10 Jan 2025 09:36:30 +0000 (UTC) Subject: [Spce-user] Invoice bug mr13.1.1 Message-ID: <872532966.1033428.1736501790663.JavaMail.zextras@connectlife.it>

Good morning, we report a bug on mr13.1.1 related to invoice generation
On the old panel when you click on Create Invoice you get:

500 Internal server error

We are terribly sorry, an exceptional error has occurred:
incident number: 18194B04606DE0F8
time of incident: 2025-01-10T09:33:33.497803000Z

On the other hand, the new panel does not display the templates, if you try to create a new template you get:

Unexpected error: Missing required param "id"

-------------- next part -------------- An HTML attachment was scrubbed... URL: From cappellari at connectlife.it Fri Jan 10 04:38:27 2025 From: cappellari at connectlife.it (Danny Cappellari) Date: Fri, 10 Jan 2025 09:38:27 +0000 (UTC) Subject: [Spce-user] Invoice bug mr13.1.1 In-Reply-To: <872532966.1033428.1736501790663.JavaMail.zextras@connectlife.it> References: <872532966.1033428.1736501790663.JavaMail.zextras@connectlife.it> Message-ID: <2132201376.1033991.1736501907853.JavaMail.zextras@connectlife.it> This output of /var/log/ngcp/panel.log Jan 10 10:32:23 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:32:23 sbc1 ngcp-panel: ERROR: fatal error, id=18194AF422305790, timestamp=2025-01-10T09:32:23.734106000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? Jan 10 10:32:54 sbc1 ngcp-panel: INFO: IP=154.60.195.1 CALLED=Controller::InvoiceTemplate::create TX=18194AFB33EBC8F0 USER=administrator DATA=?{ 'category' => 'customer', 'lang' => 'en', 'name' => 'connectlife', 'call_direction' => 'out', 'reseller.id' => '1', 'framed' => 1, 'save' => 'Save', 'submitid' => '', 'type' => 'svg'}? MSG="Invoice template successfully created" LOG="" DURATION=0.046038 Jan 10 10:33:33 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:33:33 sbc1 ngcp-panel: ERROR: fatal error, id=18194B04606DE0F8, timestamp=2025-01-10T09:33:33.497803000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? Jan 10 10:37:21 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:37:21 sbc1 ngcp-panel: ERROR: fatal error, id=18194B39886FBC40, timestamp=2025-01-10T09:37:21.802280000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? Jan 10 10:37:25 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:37:25 sbc1 ngcp-panel: ERROR: fatal error, id=18194B3A50D07D00, timestamp=2025-01-10T09:37:25.164064000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rkrenn at sipwise.com Fri Jan 10 04:47:05 2025 From: rkrenn at sipwise.com (rkrenn at sipwise.com) Date: Fri, 10 Jan 2025 10:47:05 +0100 Subject: [Spce-user] Invoice bug mr13.1.1 In-Reply-To: <2132201376.1033991.1736501907853.JavaMail.zextras@connectlife.it> References: <872532966.1033428.1736501790663.JavaMail.zextras@connectlife.it> <2132201376.1033991.1736501907853.JavaMail.zextras@connectlife.it> Message-ID: <004001db6344$9c40cce0$d4c266a0$@sipwise.com> Yes, fix is on the way. br Von: Danny Cappellari via Spce-user Gesendet: Freitag, 10. J?nner 2025 10:38 An: spce-user Betreff: Re: [Spce-user] Invoice bug mr13.1.1 This output of /var/log/ngcp/panel.log Jan 10 10:32:23 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:32:23 sbc1 ngcp-panel: ERROR: fatal error, id=18194AF422305790, timestamp=2025-01-10T09:32:23.734106000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? Jan 10 10:32:54 sbc1 ngcp-panel: INFO: IP=154.60.195.1 CALLED=Controller::InvoiceTemplate::create TX=18194AFB33EBC8F0 USER=administrator DATA=?{ 'category' => 'customer', 'lang' => 'en', 'name' => 'connectlife', 'call_direction' => 'out', 'reseller.id' => '1', 'framed' => 1, 'save' => 'Save', 'submitid' => '', 'type' => 'svg'}? MSG="Invoice template successfully created" LOG="" DURATION=0.046038 Jan 10 10:33:33 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:33:33 sbc1 ngcp-panel: ERROR: fatal error, id=18194B04606DE0F8, timestamp=2025-01-10T09:33:33.497803000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? Jan 10 10:37:21 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:37:21 sbc1 ngcp-panel: ERROR: fatal error, id=18194B39886FBC40, timestamp=2025-01-10T09:37:21.802280000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? Jan 10 10:37:25 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:37:25 sbc1 ngcp-panel: ERROR: fatal error, id=18194B3A50D07D00, timestamp=2025-01-10T09:37:25.164064000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? -------------- next part -------------- An HTML attachment was scrubbed... URL: From cappellari at connectlife.it Fri Jan 10 04:47:51 2025 From: cappellari at connectlife.it (Danny Cappellari) Date: Fri, 10 Jan 2025 09:47:51 +0000 (UTC) Subject: [Spce-user] Invoice bug mr13.1.1 In-Reply-To: <004001db6344$9c40cce0$d4c266a0$@sipwise.com> References: <872532966.1033428.1736501790663.JavaMail.zextras@connectlife.it> <2132201376.1033991.1736501907853.JavaMail.zextras@connectlife.it> <004001db6344$9c40cce0$d4c266a0$@sipwise.com> Message-ID: <116860643.1034253.1736502471419.JavaMail.zextras@connectlife.it> Thanks, good work br ? ?---- Cappellari Danny Responsabile Supporto Tecnico?|?ConnectLife S.r.l Tel.?+39 045 2081019?| Mobile:?+39 392 4206436 cappellari at connectlife.it Questo documento ? formato esclusivamente per il destinatario. Tutte le informazioni ivi contenute, compresi?eventuali allegati, sono da ritenere esclusivamente confidenziali e riservate secondo i termini del vigente D.Lgs.?196/2003 in materia di privacy e del Regolamento europeo 679/2016 ? GDPR- ?e quindi ne ? proibita l?utilizzazione?ulteriore non autorizzata. Se avete ricevuto per errore questo messaggio, Vi preghiamo cortesemente di contattare?immediatamente il mittente e cancellare la e-mail. Da: "undefined" A: "'Danny Cappellari'" , "'spce-user'" Inviato: venerd? 10 gennaio 2025 10:47 Oggetto: AW: [Spce-user] Invoice bug mr13.1.1 Yes, fix is on the way. ? br ? Von: Danny Cappellari via Spce-user Gesendet: Freitag, 10. J?nner 2025 10:38 An: spce-user Betreff: Re: [Spce-user] Invoice bug mr13.1.1 This output of /var/log/ngcp/panel.log Jan 10 10:32:23 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:32:23 sbc1 ngcp-panel: ERROR: fatal error, id=18194AF422305790, timestamp=2025-01-10T09:32:23.734106000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? Jan 10 10:32:54 sbc1 ngcp-panel: INFO: IP=154.60.195.1 CALLED=Controller::InvoiceTemplate::create TX=18194AFB33EBC8F0 USER=administrator DATA=?{ 'category' => 'customer', 'lang' => 'en', 'name' => 'connectlife', 'call_direction' => 'out', 'reseller.id' => '1', 'framed' => 1, 'save' => 'Save', 'submitid' => '', 'type' => 'svg'}? MSG="Invoice template successfully created" LOG="" DURATION=0.046038 Jan 10 10:33:33 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:33:33 sbc1 ngcp-panel: ERROR: fatal error, id=18194B04606DE0F8, timestamp=2025-01-10T09:33:33.497803000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? Jan 10 10:37:21 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:37:21 sbc1 ngcp-panel: ERROR: fatal error, id=18194B39886FBC40, timestamp=2025-01-10T09:37:21.802280000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? Jan 10 10:37:25 sbc1 ngcp-panel: ERROR: Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found" Jan 10 10:37:25 sbc1 ngcp-panel: ERROR: fatal error, id=18194B3A50D07D00, timestamp=2025-01-10T09:37:25.164064000Z, error=?Couldn't render template "invoice/create.tt: file error - invoice/create.tt: not found"? -------------- next part -------------- An HTML attachment was scrubbed... URL: From cappellari at connectlife.it Fri Jan 10 07:57:23 2025 From: cappellari at connectlife.it (Danny Cappellari) Date: Fri, 10 Jan 2025 12:57:23 +0000 (UTC) Subject: [Spce-user] Cronjob ngcp-cleanup-tools not work Message-ID: <1067053698.1042875.1736513843488.JavaMail.zextras@connectlife.it> Hello, I am reporting a bug on mr13.1.1 regarding the ngcp-cleanup-tools cleaning processes The job is scheduled to delete from the database CDRs older than 90 days. The problem is that it does not start automatically CDRs are not deleted even though the process is active on the config.yml file. We need to launch it manually from the /etc/cron.d folder cleanuptools: ?acc_cleanup_days: '90' ?archive_targetdir: /ngcp-data/backup/cdr ?binlog_days: '15' ?cdr_archive_months: '2' ?cdr_cleanup_mode: backup ?cdr_keep_days: 7 ?cdr_keep_months: '2' ?compress: gzip ?debugging: 0 ?delete_old_cdr_files: ?enable: yes ?max_age_days: '90' ?paths: ?- max_age_days: ~ ?path: /home/jail/home/*/20[0-9][0-9][0-9][0-9]/[0-9][0-9] ?remove_empty_directories: yes ?wildcard: yes ?- max_age_days: ~ ?path: /home/jail/home/cdrexport/resellers/*/20[0-9][0-9][0-9][0-9]/[0-9][0-9] ?remove_empty_directories: yes ?wildcard: yes ?- max_age_days: ~ ?path: /home/jail/home/cdrexport/system/20[0-9][0-9][0-9][0-9]/[0-9][0-9] ?remove_empty_directories: yes ?wildcard: yes -------------- next part -------------- An HTML attachment was scrubbed... URL: From ptakjura at gmail.com Sun Jan 12 12:48:27 2025 From: ptakjura at gmail.com (Jiri Ptacnik) Date: Sun, 12 Jan 2025 18:48:27 +0100 Subject: [Spce-user] [EXTERNAL] Voicemail and No audio available on SIP In-Reply-To: References:

Message-ID: Hello everyone, problem was on peering side: When they have SIP forking disabled, redirect with condition into Voicebox does not work. After SIP forking enabled, redirect is working fine. JP ?t 14. 5. 2024 v 15:58 odes?latel Jiri Ptacnik napsal: > > Thank you Marco, > > we step further: > > - We setup one network connection and it behaves same way (networks > are connected before going into Sipwise machine). Still problem with > redirect with condition to voicebox with one of our peering trunk. TCP > dump shows SIP CANCEL from our machine to peering trunk. > - So probably no network problem, or not on Sipwise machine. > - Another test shows success, when the redirect with condition is set, > but not into Voicebox, but on another number. This case works fine. So > something around Voicebox located, may be around Asterisk module (I am > not sure, if Asterisk module is in use when immediate or conditional > call into another number is in use). > > Still only one thing, what is different for this problematic peering > trunk, is that this trunk has different IP for SIP traffic and another > one for RTP > We try capture more dumps and logs... > > JiriP > > ?t 14. 5. 2024 v 9:45 odes?latel Marco Capetta via Spce-user > napsal: > > > > Hi jiri, > > > > sorry for my late reply. > > > > If I have understood properly, from your analysis the problem looks related to call routing if the calls comes from a specific network interface. > > I then suggest to investigate in the following direction: > > * capture the sip trace of a working and not working call using sngrep or tcpdump. Then you can compare and check differences. It could be that for some unknown reason the call is routed differently. > > * capture and compare kamailio proxy logs for a working and not working call and try to see if you notice any relevant difference between them. > > > > Cheers > > Marco > > > > On Thu, May 2, 2024 at 10:01?AM Jiri Ptacnik wrote: > >> > >> I have confirmed, that problem is network related. > >> > >> - When call is going through neth0, then everything works. > >> - When call is going through ens19, then redirect to voicebox after > >> specified time is not working (immediate redirect works). > >> > >> JP > >> > >> > >> ?t 2. 4. 2024 v 11:11 odes?latel Jiri Ptacnik napsal: > >> > >> > > >> > Voicemail works > >> > > >> > - when immediate redirect to voicebox is set > >> > - when ringing some time condition is set AND (!) call is made between > >> > subscribers on the same SPCE platform > >> > > >> > When call is originated for example in GSM network and is going do > >> > SPCE from outside, immediate redirect to voicebox works, conditional > >> > is NOT working. > >> > > >> > It does not seems to sounds problem related. > >> > > >> > How about this networks settings, does it looks right for you: > >> > > >> > > >> > --- > >> > hosts: > >> > self: > >> > dbnode: '1' > >> > interfaces: > >> > - lo > >> > - neth0 > >> > - ens19 > >> > lo: > >> > cluster_sets: > >> > - default > >> > eee: no > >> > ip: 127.0.0.1 > >> > netmask: 255.255.255.0 > >> > shared_ip: [] > >> > shared_v6ip: [] > >> > type: > >> > - sip_int > >> > - ha_int > >> > - aux_ext > >> > - ssh_ext > >> > - api_int > >> > - rtp_int > >> > - stor_int > >> > v6ip: ::1 > >> > v6netmask: 128 > >> > neth0: > >> > dns_nameservers: > >> > - 8.8.8.8 > >> > eee: no > >> > gateway: 111.111.111.158 > >> > hwaddr: 33:33:33:33:33:33 > >> > ip: 111.111.111.154 > >> > netmask: 255.255.255.224 > >> > type: > >> > - sip_ext > >> > - rtp_ext > >> > - web_int > >> > - ssh_ext > >> > - web_ext > >> > ens19: > >> > eee: no > >> > hwaddr: 22:22:22:22:22:22 > >> > ip: 222.222.222.150 > >> > netmask: 255.255.255.252 > >> > post_up: > >> > - route add -net 333.333.333.48/28 gw 222.222.222.149 > >> > type: > >> > - sip_ext_incoming > >> > - rtp_ext > >> > nodename: spce > >> > role: > >> > - proxy > >> > - lb > >> > - mgmt > >> > - rtp > >> > - db > >> > - storage > >> > status: online > >> > swraiddevices: [] > >> > sysdescr: '' > >> > syslocation: '' > >> > sysname: '' > >> > > >> > > >> > thanks > >> > JiriP > >> > > >> > > >> > > >> > po 25. 3. 2024 v 12:16 odes?latel Jiri Ptacnik napsal: > >> > > > >> > > When I set language for Voicebox on Domain level, then Asterisk > >> > > reporting EN for example in Digits sounds, but with same error - no > >> > > audio available. > >> > > > >> > > Also custom greetings upload works in Old admin GUI, not in New GUI. > >> > > > >> > > JiriP > >> > > > >> > > po 25. 3. 2024 v 9:54 odes?latel Jiri Ptacnik napsal: > >> > > > > >> > > > Thanks Marco, > >> > > > > >> > > > unfortunately no success. > >> > > > > >> > > > - I rised Asterisk debug level, but there is no information about > >> > > > specific missing file: I can see some messages DE language is in use, > >> > > > but this is not set for Subsriber, nor in default level (EN is set). > >> > > > > >> > > > - I also reset Soundset > >> > > > > >> > > > - Also I can see, If i try to setup custom voicemail greetings, these > >> > > > are not saved or applied, but no error message anywhere. But for > >> > > > example I have one subscriber from earlier with custom greeting and he > >> > > > still has his greetings. Also there are probably problems with saving > >> > > > language settings... > >> > > > > >> > > > Overall, this seems not directly Voicemail problem, more deeper > >> > > > problem "something goes wrong after upgrade from 9.5 do 10.5". In > >> > > > another question I have problems with redis/keydb, may be, it is some > >> > > > way related... I am looking into logs, but without luck to see > >> > > > anything clear... > >> > > > > >> > > > service.log: "No pushd defined or found..." after ngcp-status command > >> > > > sems.log: "Could not extract expires value..." > >> > > > panel.log: "Failed to find path API/attach", "Error 500..." > >> > > > redis.log: is always empty, seems strange to me... > >> > > > syslog: nothing special > >> > > > > >> > > > I think, best thing to do could be re-install system. Is there any > >> > > > best-practice for this? For example install clean SPCE of same version > >> > > > as now, then copy MySQL DB + NGCP config files to this new system...? > >> > > > > >> > > > JiriP > >> > > > > >> > > > ?t 21. 3. 2024 v 11:38 odes?latel Marco Capetta via Spce-user > >> > > > napsal: > >> > > > > > >> > > > > Hi Jiri, > >> > > > > > >> > > > > the announcement played by Asterisk in case of not answer or unconditional forward to voicemail are different. > >> > > > > Possible tests: > >> > > > > * Check that your asterisk sound packages are updated > >> > > > > * Try to switch to another of the available voicemail language and see if ti solves the problem. In this case you are most probably missing one of the announcements. > >> > > > > * Remove all the voicemail custom greetings > >> > > > > * If you enter in the astersik cli, you can also increase the verbose/debug level and get additional information about the missing file. > >> > > > > > >> > > > > Thank you > >> > > > > > >> > > > > Regards > >> > > > > Marco > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > On Thu, Mar 21, 2024 at 9:22?AM Jiri Ptacnik wrote: > >> > > > >> > >> > > > >> Hi, > >> > > > >> > >> > > > >> SPCE 10.5.6 > >> > > > >> > >> > > > >> When Redirect to Voicebox is set up (without condition, immediately), > >> > > > >> it works fine. > >> > > > >> > >> > > > >> When the condition is set (for example After 15 seconds redirect to > >> > > > >> Voicebox), then after 15 seconds ringing, the call is terminated > >> > > > >> without going into Voicebox. > >> > > > >> > >> > > > >> In voicemail.log is this: > >> > > > >> > >> > > > >> Mar 20 19:29:40 spce asterisk[611]: WARNING[4157][C-00000002]: > >> > > > >> app.c:1941 in __ast_play_and_record: No audio available on > >> > > > >> SIP/sip_proxy-00000001?? > >> > > > >> Mar 20 19:29:40 spce asterisk[611]: [Mar 20 19:29:40] > >> > > > >> #033[1;31mWARNING#033[0m[4157][C-00000002]: > >> > > > >> #033[1;37mapp.c#033[0m:#033[1;37m1941#033[0m > >> > > > >> #033[1;37m__ast_play_and_record#033[0m: No audio available on > >> > > > >> SIP/sip_proxy-00000001?? > >> > > > >> > >> > > > >> Any hints? It could be a problem with network interfaces and its Types > >> > > > >> defined in network.yml? > >> > > > >> > >> > > > >> thanks > >> > > > >> JiriP > >> > > > >> > >> > > > >> -- > >> > > > >> Spce-user mailing list > >> > > > >> Spce-user at lists.sipwise.com > >> > > > >> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com > >> > > > > > >> > > > > > >> > > > > > >> > > > > -- > >> > > > > > >> > > > > Sipwise GmbH | an Alcatel-Lucent Company > >> > > > > Leonard-Bernstein-Stra?e 10 | 1220 Wien > >> > > > > Email: invoice at sipwise.com > >> > > > > Website: https://www.sipwise.com > >> > > > > > >> > > > > Particulars according Austrian Companies Code paragraph 14 > >> > > > > Gesch?ftsf?hrer: DI Dr. Gernot Fuchs Sitz: Wien FG: Landesgericht Wien FN: 305595f > >> > > > > Die ?bermittelten Informationen sind ausschlie?lich dem Empf?nger vorbehalten und k?nnen vertrauliches oder privilegiertes Material enthalten. Ein Gebrauch, Weiterleitung oder Verbreitung in jeglicher Form seitens Dritter ist nicht gestattet. Sollten Sie diese Nachricht irrt?mlich erhalten haben, bitten wir Sie, sich mit dem Absender in Verbindung zu setzen und die Nachricht einschlie?lich der Anlagen zu l?schen. Jegliche nicht autorisierte Nutzung dieser E-Mail ist illegal. > >> > > > > Hinweis zum Datenschutz: Sipwise GmbH ist der Schutz Ihrer Daten wichtig. Auch durch die Kommunikation per E-Mail werden personenbezogene Daten ausgetauscht. Erfahren Sie mehr unter: www.sipwise.com > >> > > > > > >> > > > > Managing Director: DI Dr. Gernot Fuchs HQ: Vienna FG: Vienna Regional Court FN: 305595f > >> > > > > Confidentially notice. This e-mail transmission may contain legally privileged and/or confidential information. Please do not read it if you are not the intended recipient(s). Any use, reproduction or disclosure by any other person is prohibited. If you have received this e-mail in error, please notify the sender and destroy the original transmission and its attachments without reading or saving it in any manner. Any unauthorized use of this e-mail is illegal. > >> > > > > Note on data protection: Sipwise GmbH attaches great importance to the protection of your data. Personal data is also exchanged through communication by e-mail. Learn more at: www.sipwise.com > >> > > > > -- > >> > > > > Spce-user mailing list > >> > > > > Spce-user at lists.sipwise.com > >> > > > > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com > > > > > > > > -- > > > > Sipwise GmbH | an Alcatel-Lucent Company > > Leonard-Bernstein-Stra?e 10 | 1220 Wien > > Email: invoice at sipwise.com > > Website: https://www.sipwise.com > > > > Particulars according Austrian Companies Code paragraph 14 > > Gesch?ftsf?hrer: DI Dr. Gernot Fuchs Sitz: Wien FG: Landesgericht Wien FN: 305595f > > Die ?bermittelten Informationen sind ausschlie?lich dem Empf?nger vorbehalten und k?nnen vertrauliches oder privilegiertes Material enthalten. Ein Gebrauch, Weiterleitung oder Verbreitung in jeglicher Form seitens Dritter ist nicht gestattet. Sollten Sie diese Nachricht irrt?mlich erhalten haben, bitten wir Sie, sich mit dem Absender in Verbindung zu setzen und die Nachricht einschlie?lich der Anlagen zu l?schen. Jegliche nicht autorisierte Nutzung dieser E-Mail ist illegal. > > Hinweis zum Datenschutz: Sipwise GmbH ist der Schutz Ihrer Daten wichtig. Auch durch die Kommunikation per E-Mail werden personenbezogene Daten ausgetauscht. Erfahren Sie mehr unter: www.sipwise.com > > > > Managing Director: DI Dr. Gernot Fuchs HQ: Vienna FG: Vienna Regional Court FN: 305595f > > Confidentially notice. This e-mail transmission may contain legally privileged and/or confidential information. Please do not read it if you are not the intended recipient(s). Any use, reproduction or disclosure by any other person is prohibited. If you have received this e-mail in error, please notify the sender and destroy the original transmission and its attachments without reading or saving it in any manner. Any unauthorized use of this e-mail is illegal. > > Note on data protection: Sipwise GmbH attaches great importance to the protection of your data. Personal data is also exchanged through communication by e-mail. Learn more at: www.sipwise.com > > -- > > Spce-user mailing list > > Spce-user at lists.sipwise.com > > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com From cesarluis89 at gmail.com Sun Jan 19 08:15:15 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Sun, 19 Jan 2025 09:15:15 -0400 Subject: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot Message-ID: Hi, I?ve been trying to get a stable install of Sipwise CE for the last couple of days with no avail. Everything goes smooth per the handbook, until I reboot the server. Each time I reboot the server, nginx and prometheus-nginx-exporter fail to load, and have to be manually started by ngcp-service restart or by ngcpcfg apply which also restarts services. I have tried using the installcd, doing a clean debian with ngcp installer, and with various versions of the release, and always get the same outcome. I even tried installing 11.5 LTS and upgrading from there to 13.1.1, same thing. I checked if systemclt has something in the logs for not being able to start nginx, but nope, clear logs. After I restart the services, everything keeps working butter smooth until the server gets rebooted again, which is not reliable for production. This is running on a SuperMicro blade, dedicated host, no VMs. I have come to the conclusion that there might be some kernel issue with this hardware, but I cannot replicate the issue with a clean Debian install. Any help is appreciated! Cesar From walter at myrepublic.net Sun Jan 19 08:35:28 2025 From: walter at myrepublic.net (Walter Klomp) Date: Sun, 19 Jan 2025 21:35:28 +0800 Subject: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: References: Message-ID: After rebooting you need to do an ngcp-initial-install if memory serves me right. Just continue with the manual after the reboot. [image: Signature image] Walter Klomp Head of Voice Network [image: Email] walter at myrepublic.net Beyond Work : 11 Lorong 3 Toa Payoh, #04-11/15, Jackson Square, Block B, Singapore 319579 www.myrepublic.net * [image: Facebook-f] * * [image: Instagram] * * [image: Twitter] * * [image: Linkedin-in] * The information in this message is privileged and confidential. If you are not the intended recipient of this email, please don't read, copy, use, distribute or tell anyone about it; kindly destroy it and notify the sender by return email. Please advise immediately if you or your employer does not consent to email for messages of this kind. Any content that is not concerned with MyRepublic business reflects the views of the sender only and not those of MyRepublic. [image: Signature header] On Sun, 19 Jan 2025 at 21:16, Cesar Mora wrote: > Hi, > > I?ve been trying to get a stable install of Sipwise CE for the last couple > of days with no avail. Everything goes smooth per the handbook, until I > reboot the server. Each time I reboot the server, nginx and > prometheus-nginx-exporter fail to load, and have to be manually started by > ngcp-service restart or by ngcpcfg apply which also restarts services. I > have tried using the installcd, doing a clean debian with ngcp installer, > and with various versions of the release, and always get the same outcome. > I even tried installing 11.5 LTS and upgrading from there to 13.1.1, same > thing. I checked if systemclt has something in the logs for not being able > to start nginx, but nope, clear logs. After I restart the services, > everything keeps working butter smooth until the server gets rebooted > again, which is not reliable for production. > > This is running on a SuperMicro blade, dedicated host, no VMs. I have come > to the conclusion that there might be some kernel issue with this hardware, > but I cannot replicate the issue with a clean Debian install. > > Any help is appreciated! > > Cesar > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com > -- The contents of this email and any attachments are confidential and may also be privileged. You must not disseminate the contents of this email and any attachments without permission of the sender. If you have received this email by mistake, please delete all copies and inform the sender immediately. You may refer to our company's Privacy Policy here . -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesarluis89 at gmail.com Sun Jan 19 09:19:59 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Sun, 19 Jan 2025 14:19:59 +0000 Subject: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: References:

Message-ID: Yup, done all that per the manual, otherwise the install is incomplete and won?t run. 1. boot with install cd 2. Setup network interface 3. Wait until full install is complete and asks for the first reboot. 4. After first reboot, go into terminal multiplexer and run ngcp-initial-configuration. 5. Move listening services from lo to neth0 (interface name in my case). 6. Run first ngcpcfg apply ?net config change? 7. Reboot again. 8. Config.yml is now updated with new listening interface name, run ngcpcfg apply ?added network interface? 9. Now everything works perfectly fine, I added peering server, registered some test customers, all good! Everything will keep working perfectly until I reboot the server for any reason. The server will boot, sip services work, ssh works, but ngix service will fail to boot, so no web UI. ngcp-services shows ngix and prometeus-ngix-exporter are managed and on-boot but status is failed to start. Manually restarting them will get them up and running, but this is not the expected behaviour. Btw, ngcp-rate-o-mat service will start on boot, but also fails after the server has been running for a while, but doesn?t seem to affect anything vital. Get Outlook for iOS ________________________________ From: Walter Klomp Sent: Sunday, January 19, 2025 9:35:28 AM To: Cesar Mora Cc: spce-user at lists.sipwise.com Subject: Re: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot After rebooting you need to do an ngcp-initial-install if memory serves me right. Just continue with the manual after the reboot. [Signature image] Walter Klomp Head of Voice Network [Email] walter at myrepublic.net Beyond Work : 11 Lorong 3 Toa Payoh, #04-11/15, Jackson Square, Block B, Singapore 319579 www.myrepublic.net [Facebook-f] [Instagram] [Twitter] [Linkedin-in] The information in this message is privileged and confidential. If you are not the intended recipient of this email, please don't read, copy, use, distribute or tell anyone about it; kindly destroy it and notify the sender by return email. Please advise immediately if you or your employer does not consent to email for messages of this kind. Any content that is not concerned with MyRepublic business reflects the views of the sender only and not those of MyRepublic. On Sun, 19 Jan 2025 at 21:16, Cesar Mora > wrote: Hi, I?ve been trying to get a stable install of Sipwise CE for the last couple of days with no avail. Everything goes smooth per the handbook, until I reboot the server. Each time I reboot the server, nginx and prometheus-nginx-exporter fail to load, and have to be manually started by ngcp-service restart or by ngcpcfg apply which also restarts services. I have tried using the installcd, doing a clean debian with ngcp installer, and with various versions of the release, and always get the same outcome. I even tried installing 11.5 LTS and upgrading from there to 13.1.1, same thing. I checked if systemclt has something in the logs for not being able to start nginx, but nope, clear logs. After I restart the services, everything keeps working butter smooth until the server gets rebooted again, which is not reliable for production. This is running on a SuperMicro blade, dedicated host, no VMs. I have come to the conclusion that there might be some kernel issue with this hardware, but I cannot replicate the issue with a clean Debian install. Any help is appreciated! Cesar -- Spce-user mailing list Spce-user at lists.sipwise.com http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com The contents of this email and any attachments are confidential and may also be privileged. You must not disseminate the contents of this email and any attachments without permission of the sender. If you have received this email by mistake, please delete all copies and inform the sender immediately. You may refer to our company's Privacy Policy here. -------------- next part -------------- An HTML attachment was scrubbed... URL: From walter at myrepublic.net Sun Jan 19 09:31:24 2025 From: walter at myrepublic.net (Walter Klomp) Date: Sun, 19 Jan 2025 22:31:24 +0800 Subject: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: References:

Message-ID: Maybe do have a look at why nginx doesn?t boot. The logs are all in /var/log/nginx and in /var/log/ngcp Rate-o-mat depends on valid billing entries. Will not affect operations but will affect credit control and CDR etc?. Are you using any let?s encrypt certificates? I?m running 12.5.1 as CE and other than a known bug on admin access rights it should just work out of the box. And I installed it from installer CD. Just try to not update it to development 13.x first. Regards Walter. [image: Signature header] On Sun, 19 Jan 2025 at 22:20, Cesar Mora wrote: > Yup, done all that per the manual, otherwise the install is incomplete and > won?t run. > > > 1. boot with install cd > 2. Setup network interface > 3. Wait until full install is complete and asks for the first reboot. > 4. After first reboot, go into terminal multiplexer and run > ngcp-initial-configuration. > 5. Move listening services from lo to neth0 (interface name in my > case). > 6. Run first ngcpcfg apply ?net config change? > 7. Reboot again. > 8. Config.yml is now updated with new listening interface name, run > ngcpcfg apply ?added network interface? > 9. Now everything works perfectly fine, I added peering server, > registered some test customers, all good! > > > Everything will keep working perfectly until I reboot the server for any > reason. The server will boot, sip services work, ssh works, but ngix > service will fail to boot, so no web UI. ngcp-services shows ngix and > prometeus-ngix-exporter are managed and on-boot but status is failed to > start. Manually restarting them will get them up and running, but this is > not the expected behaviour. Btw, ngcp-rate-o-mat service will start on > boot, but also fails after the server has been running for a while, but > doesn?t seem to affect anything vital. > > Get Outlook for iOS > ------------------------------ > *From:* Walter Klomp > *Sent:* Sunday, January 19, 2025 9:35:28 AM > *To:* Cesar Mora > *Cc:* spce-user at lists.sipwise.com > *Subject:* Re: [Spce-user] nginx and prometheus-nginx-exporter fail to > load after reboot > > After rebooting you need to do an ngcp-initial-install if memory serves me > right. Just continue with the manual after the reboot. > > [image: Signature image] > Walter Klomp > Head of Voice Network > [image: Email] walter at myrepublic.net > Beyond Work : > 11 Lorong 3 Toa Payoh, #04 > -11/15, > Jackson Square, Block B, Singapore 319579 > www.myrepublic.net > *[image: Facebook-f] * *[image: > Instagram] * *[image: > Twitter] * *[image: > Linkedin-in] * > The information in this message is privileged and confidential. If you are > not the intended recipient of this email, please don't read, copy, use, > distribute or tell anyone about it; kindly destroy it and notify the sender > by return email. Please advise immediately if you or your employer does not > consent to email for messages of this kind. Any content that is not > concerned with MyRepublic business reflects the views of the sender only > and not those of MyRepublic. > [image: Signature header] > > > On Sun, 19 Jan 2025 at 21:16, Cesar Mora wrote: > > Hi, > > I?ve been trying to get a stable install of Sipwise CE for the last couple > of days with no avail. Everything goes smooth per the handbook, until I > reboot the server. Each time I reboot the server, nginx and > prometheus-nginx-exporter fail to load, and have to be manually started by > ngcp-service restart or by ngcpcfg apply which also restarts services. I > have tried using the installcd, doing a clean debian with ngcp installer, > and with various versions of the release, and always get the same outcome. > I even tried installing 11.5 LTS and upgrading from there to 13.1.1, same > thing. I checked if systemclt has something in the logs for not being able > to start nginx, but nope, clear logs. After I restart the services, > everything keeps working butter smooth until the server gets rebooted > again, which is not reliable for production. > > This is running on a SuperMicro blade, dedicated host, no VMs. I have come > to the conclusion that there might be some kernel issue with this hardware, > but I cannot replicate the issue with a clean Debian install. > > Any help is appreciated! > > Cesar > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com > > > The contents of this email and any attachments are confidential and may > also be privileged. You must not disseminate the contents of this email and > any attachments without permission of the sender. If you have received this > email by mistake, please delete all copies and inform the sender > immediately. You may refer to our company's Privacy Policy here > . > -- The contents of this email and any attachments are confidential and may also be privileged. You must not disseminate the contents of this email and any attachments without permission of the sender. If you have received this email by mistake, please delete all copies and inform the sender immediately. You may refer to our company's Privacy Policy here . -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesarluis89 at gmail.com Sun Jan 19 09:58:45 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Sun, 19 Jan 2025 14:58:45 +0000 Subject: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: References:

Message-ID: I?m sorry, I said 11.5 LTS but it is actually 12.5.1 LTS. I tried upgrading to 13 at one point to see if it solved the issue, but the problem persisted, so I did another 12.5.1 clean install. No certificates, all default config. The problem will arise as soon as you reboot after installation is fully done, regardless it is a clean slate install, or data has been added to it. I also encountered the admin problem as soon as I changed the password for administrator. Role changes to (reseller). I had to go into the database and change the administrator account to is_system as a work around. I thought it was something I had done wrong, but I saw it again after a clean install, so I assumed it was a bug. As for the logs, that is the puzzling part? /var/log/nginx/error.log is empty /var/log/ngcp/nginx/error.log is also empty When the server boots, right before the login prompt shows up, you can see: [FAILED] Failed to start nginx.service - A high performance web server and a reverse proxy server. [FAILED] Failed to start prometheus-nginx-exporter.service - NGINX Prometheus Exporter. Get Outlook for iOS ________________________________ From: Walter Klomp Sent: Sunday, January 19, 2025 10:31:24 AM To: Cesar Mora Cc: spce-user at lists.sipwise.com Subject: Re: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot Maybe do have a look at why nginx doesn?t boot. The logs are all in /var/log/nginx and in /var/log/ngcp Rate-o-mat depends on valid billing entries. Will not affect operations but will affect credit control and CDR etc?. Are you using any let?s encrypt certificates? I?m running 12.5.1 as CE and other than a known bug on admin access rights it should just work out of the box. And I installed it from installer CD. Just try to not update it to development 13.x first. Regards Walter. On Sun, 19 Jan 2025 at 22:20, Cesar Mora > wrote: Yup, done all that per the manual, otherwise the install is incomplete and won?t run. 1. boot with install cd 2. Setup network interface 3. Wait until full install is complete and asks for the first reboot. 4. After first reboot, go into terminal multiplexer and run ngcp-initial-configuration. 5. Move listening services from lo to neth0 (interface name in my case). 6. Run first ngcpcfg apply ?net config change? 7. Reboot again. 8. Config.yml is now updated with new listening interface name, run ngcpcfg apply ?added network interface? 9. Now everything works perfectly fine, I added peering server, registered some test customers, all good! Everything will keep working perfectly until I reboot the server for any reason. The server will boot, sip services work, ssh works, but ngix service will fail to boot, so no web UI. ngcp-services shows ngix and prometeus-ngix-exporter are managed and on-boot but status is failed to start. Manually restarting them will get them up and running, but this is not the expected behaviour. Btw, ngcp-rate-o-mat service will start on boot, but also fails after the server has been running for a while, but doesn?t seem to affect anything vital. Get Outlook for iOS ________________________________ From: Walter Klomp > Sent: Sunday, January 19, 2025 9:35:28 AM To: Cesar Mora > Cc: spce-user at lists.sipwise.com

> Subject: Re: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot After rebooting you need to do an ngcp-initial-install if memory serves me right. Just continue with the manual after the reboot. [Signature image] Walter Klomp Head of Voice Network [Email] walter at myrepublic.net Beyond Work : 11 Lorong 3 Toa Payoh, #04-11/15, Jackson Square, Block B, Singapore 319579 www.myrepublic.net [Facebook-f] [Instagram] [Twitter] [Linkedin-in] The information in this message is privileged and confidential. If you are not the intended recipient of this email, please don't read, copy, use, distribute or tell anyone about it; kindly destroy it and notify the sender by return email. Please advise immediately if you or your employer does not consent to email for messages of this kind. Any content that is not concerned with MyRepublic business reflects the views of the sender only and not those of MyRepublic. On Sun, 19 Jan 2025 at 21:16, Cesar Mora > wrote: Hi, I?ve been trying to get a stable install of Sipwise CE for the last couple of days with no avail. Everything goes smooth per the handbook, until I reboot the server. Each time I reboot the server, nginx and prometheus-nginx-exporter fail to load, and have to be manually started by ngcp-service restart or by ngcpcfg apply which also restarts services. I have tried using the installcd, doing a clean debian with ngcp installer, and with various versions of the release, and always get the same outcome. I even tried installing 11.5 LTS and upgrading from there to 13.1.1, same thing. I checked if systemclt has something in the logs for not being able to start nginx, but nope, clear logs. After I restart the services, everything keeps working butter smooth until the server gets rebooted again, which is not reliable for production. This is running on a SuperMicro blade, dedicated host, no VMs. I have come to the conclusion that there might be some kernel issue with this hardware, but I cannot replicate the issue with a clean Debian install. Any help is appreciated! Cesar -- Spce-user mailing list Spce-user at lists.sipwise.com http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com The contents of this email and any attachments are confidential and may also be privileged. You must not disseminate the contents of this email and any attachments without permission of the sender. If you have received this email by mistake, please delete all copies and inform the sender immediately. You may refer to our company's Privacy Policy here. The contents of this email and any attachments are confidential and may also be privileged. You must not disseminate the contents of this email and any attachments without permission of the sender. If you have received this email by mistake, please delete all copies and inform the sender immediately. You may refer to our company's Privacy Policy here. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mprokop at sipwise.com Mon Jan 20 04:07:02 2025 From: mprokop at sipwise.com (Michael Prokop) Date: Mon, 20 Jan 2025 10:07:02 +0100 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: References:

Message-ID: <2025-01-20T09-58-04@devnull.michael-prokop.at> Hi, * Cesar Mora [Sun Jan 19, 2025 at 02:58:45PM +0000]: > I?m sorry, I said 11.5 LTS but it is actually 12.5.1 LTS. I tried > upgrading to 13 at one point to see if it solved the issue, but > the problem persisted, so I did another 12.5.1 clean install. No > certificates, all default config. The problem will arise as soon > as you reboot after installation is fully done, regardless it is a > clean slate install, or data has been added to it. [...] > As for the logs, that is the puzzling part? > > /var/log/nginx/error.log is empty > /var/log/ngcp/nginx/error.log is also empty > > When the server boots, right before the login prompt shows up, you can see: > > [FAILED] Failed to start nginx.service - A high performance web server and a reverse proxy server. > > [FAILED] Failed to start prometheus-nginx-exporter.service - NGINX Prometheus Exporter. What's inside your syslog (/var/log/syslog)? If that shouldn't provide any further information for you, try enabling journald: ngcpcfg set /etc/ngcp-config/config.yml systemd.journald.storage=auto ngcpcfg apply "enable journald" Then check out "journalctl -u nginx" after rebooting. regards -mika- From cesarluis89 at gmail.com Wed Jan 22 09:43:00 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Wed, 22 Jan 2025 10:43:00 -0400 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <2025-01-20T09-58-04@devnull.michael-prokop.at> References:

<2025-01-20T09-58-04@devnull.michael-prokop.at> Message-ID: <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> Syslog shows that nginx will be commanded for start, but later will fail with: Jan 22 10:12:00 spce systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE Jan 22 10:12:00 spce systemd[1]: nginx.service: Failed with result 'exit-code?. Prometheus fails as well, but I guess it is nginx dependent: Jan 22 10:12:00 spce systemd[1]: prometheus-nginx-exporter.service: Main process exited, code=exited, status=1/FAILURE Jan 22 10:12:00 spce systemd[1]: prometheus-nginx-exporter.service: Failed with result 'exit-code?. I also see that prometheus will try to restart: Jan 22 10:12:01 spce systemd[1]: prometheus-nginx-exporter.service: Scheduled restart job, restart counter is at 2. Jan 22 10:12:01 spce systemd[1]: Stopped prometheus-nginx-exporter.service - NGINX Prometheus Exporter. Jan 22 10:12:01 spce systemd[1]: Started prometheus-nginx-exporter.service - NGINX Prometheus Exporter. But nginx does not try to restart... I also noticed before that ngcp-status will not work after at least 10 minutes after server starts, but could be unrelated, and I see this on the log: Jan 22 10:12:01 spce systemd[1]: Starting ngcp-panel.service - NGCP Panel Webapp... Jan 22 10:12:01 spce rmmod[1098]: rmmod: ERROR: Module ngcp is not currently loaded > On Jan 20, 2025, at 5:07?AM, Michael Prokop via Spce-user wrote: > > Hi, > > * Cesar Mora [Sun Jan 19, 2025 at 02:58:45PM +0000]: > >> I?m sorry, I said 11.5 LTS but it is actually 12.5.1 LTS. I tried >> upgrading to 13 at one point to see if it solved the issue, but >> the problem persisted, so I did another 12.5.1 clean install. No >> certificates, all default config. The problem will arise as soon >> as you reboot after installation is fully done, regardless it is a >> clean slate install, or data has been added to it. > > [...] > >> As for the logs, that is the puzzling part? >> >> /var/log/nginx/error.log is empty >> /var/log/ngcp/nginx/error.log is also empty >> >> When the server boots, right before the login prompt shows up, you can see: >> >> [FAILED] Failed to start nginx.service - A high performance web server and a reverse proxy server. >> >> [FAILED] Failed to start prometheus-nginx-exporter.service - NGINX Prometheus Exporter. > > What's inside your syslog (/var/log/syslog)? > > If that shouldn't provide any further information for you, > try enabling journald: > > ngcpcfg set /etc/ngcp-config/config.yml systemd.journald.storage=auto > ngcpcfg apply "enable journald" > > Then check out "journalctl -u nginx" after rebooting. > > regards > -mika- > > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com From mprokop at sipwise.com Wed Jan 22 09:47:43 2025 From: mprokop at sipwise.com (Michael Prokop) Date: Wed, 22 Jan 2025 15:47:43 +0100 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> References:

<2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> Message-ID: <2025-01-22T15-45-29@devnull.michael-prokop.at> Hi, * Cesar Mora [Wed Jan 22, 2025 at 10:43:00AM -0400]: > Syslog shows that nginx will be commanded for start, but later will fail with: > > Jan 22 10:12:00 spce systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE > Jan 22 10:12:00 spce systemd[1]: nginx.service: Failed with result 'exit-code?. [...] > But nginx does not try to restart... The relevant messages should be there *before* those lines. But as I wrote in my previous mail, if you don't see why it's failing from syslog, enable journald and see what you get there. regards -mika- From cesarluis89 at gmail.com Wed Jan 22 10:04:02 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Wed, 22 Jan 2025 11:04:02 -0400 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <2025-01-22T15-45-29@devnull.michael-prokop.at> References:

<2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> Message-ID: root at spce:~# journalctl -u nginx Jan 22 10:57:53 spce systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server... Jan 22 10:57:53 spce nginx[688]: 2025/01/22 10:57:53 [emerg] 688#688: a duplicate listen 127.0.0.1:8081 in /etc/nginx/sites-enabled/nginx> Jan 22 10:57:53 spce nginx[688]: nginx: configuration file /etc/nginx/nginx.conf test failed Jan 22 10:57:53 spce systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE Jan 22 10:57:53 spce systemd[1]: nginx.service: Failed with result 'exit-code'. Jan 22 10:57:53 spce systemd[1]: Failed to start nginx.service - A high performance web server and a reverse proxy server. lines 1-6/6 (END) > On Jan 22, 2025, at 10:47?AM, Michael Prokop via Spce-user wrote: > > Hi, > > * Cesar Mora [Wed Jan 22, 2025 at 10:43:00AM -0400]: > >> Syslog shows that nginx will be commanded for start, but later will fail with: >> >> Jan 22 10:12:00 spce systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE >> Jan 22 10:12:00 spce systemd[1]: nginx.service: Failed with result 'exit-code?. > [...] >> But nginx does not try to restart... > > The relevant messages should be there *before* those lines. > But as I wrote in my previous mail, if you don't see why it's > failing from syslog, enable journald and see what you get there. > > regards > -mika- > > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com From mprokop at sipwise.com Wed Jan 22 10:27:36 2025 From: mprokop at sipwise.com (Michael Prokop) Date: Wed, 22 Jan 2025 16:27:36 +0100 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: References:

<2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> Message-ID: <2025-01-22T16-24-09@devnull.michael-prokop.at> Hi, * Cesar Mora [Wed Jan 22, 2025 at 11:04:02AM -0400]: > root at spce:~# journalctl -u nginx > Jan 22 10:57:53 spce systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server... > Jan 22 10:57:53 spce nginx[688]: 2025/01/22 10:57:53 [emerg] 688#688: a duplicate listen 127.0.0.1:8081 in /etc/nginx/sites-enabled/nginx> And there we go. What do you have inside /etc/nginx/sites-enabled/nginx and what are the files looking like, where port 8081 is referred to? (One of them should be /etc/nginx/sites-available/nginx-status) regards -mika- From cesarluis89 at gmail.com Wed Jan 22 10:48:23 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Wed, 22 Jan 2025 11:48:23 -0400 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <2025-01-22T16-24-09@devnull.michael-prokop.at> References:

<2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> <2025-01-22T16-24-09@devnull.michael-prokop.at> Message-ID: That?s weird, I haven?t directly modified any of those files in any of the clean installations I did, and the problem always shows up. All I can think of is that something gets messed up in there when I perform the initial "ngcp-network? to define neth0 as the main interface (my server has 2 NICs) with: "ngcp-network --set-interface=neth0 --ip=auto --netmask=auto --hwaddr=auto? And also to move the listening services from lo to neth0 with: "ngcp-network --move-from=lo --move-to=neth0 --type=web_ext --type=sip_ext --type=rtp_ext --type=ssh_ext --type=web_int? Anyways? The files under /etc/nginx/sites-enabled/ look as: root at spce:/etc/nginx/sites-enabled# ls ngcp-panel_admin_api ngcp-panel_csc ngcp-panel_system_api nginx-status And inside nginx-status is: server { listen localhost:8081; #server_name localhost; location /nginx_status { stub_status on; access_log off; allow 127.0.0.1; allow ::1; deny all; } } Cesar > On Jan 22, 2025, at 11:27?AM, Michael Prokop via Spce-user wrote: > > Hi, > > * Cesar Mora [Wed Jan 22, 2025 at 11:04:02AM -0400]: > >> root at spce:~# journalctl -u nginx >> Jan 22 10:57:53 spce systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server... >> Jan 22 10:57:53 spce nginx[688]: 2025/01/22 10:57:53 [emerg] 688#688: a duplicate listen 127.0.0.1:8081 in /etc/nginx/sites-enabled/nginx> > > And there we go. > > What do you have inside /etc/nginx/sites-enabled/nginx and what are > the files looking like, where port 8081 is referred to? (One of them > should be /etc/nginx/sites-available/nginx-status) > > regards > -mika- > > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com From gjover at sipwise.com Wed Jan 22 14:42:49 2025 From: gjover at sipwise.com (Guillem Jover) Date: Wed, 22 Jan 2025 20:42:49 +0100 Subject: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: References:

Message-ID: Hi! On Sun, 2025-01-19 at 14:58:45 +0000, Cesar Mora wrote: > As for the logs, that is the puzzling part? > > /var/log/nginx/error.log is empty > /var/log/ngcp/nginx/error.log is also empty > > When the server boots, right before the login prompt shows up, you > can see: > > [FAILED] Failed to start nginx.service - A high performance web server and a reverse proxy server. This is the real problem, you'd need to try to check why nginx is failing to start. > [FAILED] Failed to start prometheus-nginx-exporter.service - NGINX Prometheus Exporter. This is a known limitation from this prometheus exporter, which fails to start if nginx is not running. This has been fixed upstream with https://github.com/nginx/nginx-prometheus-exporter/pull/504, so on the future NGCP release where we rebase on top of Debian trixie, we'll get that new fixed behavior. Thanks, Guillem From cesarluis89 at gmail.com Fri Jan 24 14:16:22 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Fri, 24 Jan 2025 15:16:22 -0400 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <2025-01-22T16-24-09@devnull.michael-prokop.at> References:

<2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> <2025-01-22T16-24-09@devnull.michael-prokop.at> Message-ID: <258FE5CF-896D-4682-A62C-6A892FB49E32@gmail.com> I haven?t modified any of these files. All I can think of is that something gets messed up in there when I perform the initial "ngcp-network? to define neth0 as the main interface (my server has 2 NICs) with: "ngcp-network --set-interface=neth0 --ip=auto --netmask=auto --hwaddr=auto? And also to move the listening services from lo to neth0 with: "ngcp-network --move-from=lo --move-to=neth0 --type=web_ext --type=sip_ext --type=rtp_ext --type=ssh_ext --type=web_int? Anyways? The files under /etc/nginx/sites-enabled/ look as: root at spce:/etc/nginx/sites-enabled# ls ngcp-panel_admin_api ngcp-panel_csc ngcp-panel_system_api nginx-status And inside nginx-status is: server { listen localhost:8081; #server_name localhost; location /nginx_status { stub_status on; access_log off; allow 127.0.0.1; allow ::1; deny all; } } Cesar > On Jan 22, 2025, at 11:27?AM, Michael Prokop via Spce-user wrote: > > Hi, > > * Cesar Mora [Wed Jan 22, 2025 at 11:04:02AM -0400]: > >> root at spce:~# journalctl -u nginx >> Jan 22 10:57:53 spce systemd[1]: Starting nginx.service - A high performance web server and a reverse proxy server... >> Jan 22 10:57:53 spce nginx[688]: 2025/01/22 10:57:53 [emerg] 688#688: a duplicate listen 127.0.0.1:8081 in /etc/nginx/sites-enabled/nginx> > > And there we go. > > What do you have inside /etc/nginx/sites-enabled/nginx and what are > the files looking like, where port 8081 is referred to? (One of them > should be /etc/nginx/sites-available/nginx-status) > > regards > -mika- > > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com From mprokop at sipwise.com Mon Jan 27 03:05:55 2025 From: mprokop at sipwise.com (Michael Prokop) Date: Mon, 27 Jan 2025 09:05:55 +0100 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <258FE5CF-896D-4682-A62C-6A892FB49E32@gmail.com> References: <2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> <2025-01-22T16-24-09@devnull.michael-prokop.at> <258FE5CF-896D-4682-A62C-6A892FB49E32@gmail.com> Message-ID: <2025-01-27T09-03-31@devnull.michael-prokop.at> Hi, * Cesar Mora [Fri Jan 24, 2025 at 03:16:22PM -0400]: > I haven?t modified any of these files. All I can think of is that something gets messed up in there when I perform the initial "ngcp-network? to define neth0 as the main interface (my server has 2 NICs) with: [...] > Anyways? The files under /etc/nginx/sites-enabled/ look as: > > root at spce:/etc/nginx/sites-enabled# ls > ngcp-panel_admin_api ngcp-panel_csc ngcp-panel_system_api nginx-status > > And inside nginx-status is: > > server { > listen localhost:8081; > #server_name localhost; > > location /nginx_status { > stub_status on; > access_log off; > allow 127.0.0.1; > allow ::1; > deny all; > } > } This looks ok, but as already written: > > On Jan 22, 2025, at 11:27?AM, Michael Prokop via Spce-user wrote: > > What do you have inside /etc/nginx/sites-enabled/nginx and what are > > the files looking like, where port 8081 is referred to? (One of them > > should be /etc/nginx/sites-available/nginx-status) You seem to have another file which uses port 8081. regards -mika- From bijum0888 at gmail.com Mon Jan 27 03:48:55 2025 From: bijum0888 at gmail.com (Biju K) Date: Mon, 27 Jan 2025 14:18:55 +0530 Subject: [Spce-user] nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: References: Message-ID: You may configure the service for auto start using chkconfig or systemctl enable command. Alternatively, add the service start commands on the /etc/ini.t/ folder as run scripts which will initiate on every system restarts. ~Biju K On Sun, 19 Jan 2025, 6:46?pm Cesar Mora, wrote: > Hi, > > I?ve been trying to get a stable install of Sipwise CE for the last couple > of days with no avail. Everything goes smooth per the handbook, until I > reboot the server. Each time I reboot the server, nginx and > prometheus-nginx-exporter fail to load, and have to be manually started by > ngcp-service restart or by ngcpcfg apply which also restarts services. I > have tried using the installcd, doing a clean debian with ngcp installer, > and with various versions of the release, and always get the same outcome. > I even tried installing 11.5 LTS and upgrading from there to 13.1.1, same > thing. I checked if systemclt has something in the logs for not being able > to start nginx, but nope, clear logs. After I restart the services, > everything keeps working butter smooth until the server gets rebooted > again, which is not reliable for production. > > This is running on a SuperMicro blade, dedicated host, no VMs. I have come > to the conclusion that there might be some kernel issue with this hardware, > but I cannot replicate the issue with a clean Debian install. > > Any help is appreciated! > > Cesar > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesarluis89 at gmail.com Mon Jan 27 05:02:36 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Mon, 27 Jan 2025 10:02:36 +0000 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <2025-01-27T09-03-31@devnull.michael-prokop.at> References: <2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> <2025-01-22T16-24-09@devnull.michael-prokop.at> <258FE5CF-896D-4682-A62C-6A892FB49E32@gmail.com> <2025-01-27T09-03-31@devnull.michael-prokop.at> Message-ID: Thanks for the reply! Yes, as I included in the previous message: root at spce:/etc/nginx/sites-enabled# ls ngcp-panel_admin_api ngcp-panel_csc ngcp-panel_system_api nginx-status There is no file or directory called nginx in /etc/nginx/sites-enabled/. What you see there is what is in there. Inside /etc/nginx/sites-enabled are: gcp-panel_admin_api ngcp-panel_csc ngcp-panel_system_api nginx-status And the nginx-status file in there contains what I posted earlier. I also want to add, I tried a clean install on a VirtualBox for testing, and I was able to get a full clean install with no nginx problems. The difference is that my physical server has 2 NICs and after ?ngcp-initial-config? you cannot access web or anything, and I had to do ngcp-network to move the listening services over to neth0, but the virtualbox machine with only one eth0 NIC did not need this step, and already had the listening port's at eth0 and working out of the box. So my install seems to get messed up after ngcp-network for being a physical server, and not a VM with 1 NIC with default eth0 name. Get Outlook for iOS ________________________________ From: Michael Prokop via Spce-user Sent: Monday, January 27, 2025 4:05:55 AM To: spce-user at lists.sipwise.com Subject: Re: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot Hi, * Cesar Mora [Fri Jan 24, 2025 at 03:16:22PM -0400]: > I haven?t modified any of these files. All I can think of is that something gets messed up in there when I perform the initial "ngcp-network? to define neth0 as the main interface (my server has 2 NICs) with: [...] > Anyways? The files under /etc/nginx/sites-enabled/ look as: > > root at spce:/etc/nginx/sites-enabled# ls > ngcp-panel_admin_api ngcp-panel_csc ngcp-panel_system_api nginx-status > > And inside nginx-status is: > > server { > listen localhost:8081; > #server_name localhost; > > location /nginx_status { > stub_status on; > access_log off; > allow 127.0.0.1; > allow ::1; > deny all; > } > } This looks ok, but as already written: > > On Jan 22, 2025, at 11:27?AM, Michael Prokop via Spce-user wrote: > > What do you have inside /etc/nginx/sites-enabled/nginx and what are > > the files looking like, where port 8081 is referred to? (One of them > > should be /etc/nginx/sites-available/nginx-status) You seem to have another file which uses port 8081. regards -mika- -- Spce-user mailing list Spce-user at lists.sipwise.com http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mprokop at sipwise.com Mon Jan 27 05:08:13 2025 From: mprokop at sipwise.com (Michael Prokop) Date: Mon, 27 Jan 2025 11:08:13 +0100 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: References: <2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> <2025-01-22T16-24-09@devnull.michael-prokop.at> <258FE5CF-896D-4682-A62C-6A892FB49E32@gmail.com> <2025-01-27T09-03-31@devnull.michael-prokop.at> Message-ID: <2025-01-27T11-03-37@devnull.michael-prokop.at> Hi, * Cesar Mora [Mon Jan 27, 2025 at 10:02:36AM +0000]: > Thanks for the reply! Yes, as I included in the previous message: > > root at spce:/etc/nginx/sites-enabled# ls > ngcp-panel_admin_api ngcp-panel_csc ngcp-panel_system_api nginx-status > > There is no file or directory called nginx in /etc/nginx/sites-enabled/. What you see there is what is in there. Inside /etc/nginx/sites-enabled are: [...] It's about all the files inside the /etc/nginx directory, not a file named "nginx" inside /etc/nginx/sites-enabled. But if there really is no other file referring to port 8081, this is about the issue that Guillem already pointed you to. quoting from his mail: | This is a known limitation from this prometheus exporter, which fails | to start if nginx is not running. This has been fixed upstream with | https://github.com/nginx/nginx-prometheus-exporter/pull/504, so on | the future NGCP release where we rebase on top of Debian trixie, | we'll get that new fixed behavior. PS: No need to Cc me, I'm subscribed to the mailing list. regards -mika- From cesarluis89 at gmail.com Mon Jan 27 06:18:38 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Mon, 27 Jan 2025 07:18:38 -0400 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <2025-01-27T11-03-37@devnull.michael-prokop.at> References: <2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> <2025-01-22T16-24-09@devnull.michael-prokop.at> <258FE5CF-896D-4682-A62C-6A892FB49E32@gmail.com> <2025-01-27T09-03-31@devnull.michael-prokop.at> <2025-01-27T11-03-37@devnull.michael-prokop.at> Message-ID: <4260F328-6531-49F7-9824-8433B98B4392@gmail.com> I?m so sorry! My email client keeps messing up the TO address. I found a conflict of port 8081 with nginx and tproxy, not sure if this is a part of nginx. root at spce:/# grep -Rn "tproxy" /etc/ngcp-config/ /etc/ngcp-config/templates/etc/services.tt2:339:tproxy 8081/tcp # Transparent Proxy /etc/ngcp-config/templates/etc/services.tt2:383:#nginx-status [% nginx.status_port %]/tcp # Conflicts with tproxy /etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.tt2:921: # for BYE, mark whether or not to stop rtproxy root at spce:/# Further digging, I only found 2 references to port 8081 on /etc/nginx/ root at spce:~# grep -Rn "8081" /etc/nginx/ /etc/nginx/sites-enabled/nginx-status:2: listen localhost:8081; /etc/nginx/sites-available/nginx-status:2: listen localhost:8081; But I?m guessing the sites-enabled entry is a symlink Other than this, only tproxy refers to 8081 under the config. > On Jan 27, 2025, at 6:08?AM, Michael Prokop via Spce-user wrote: > > Hi, > > * Cesar Mora [Mon Jan 27, 2025 at 10:02:36AM +0000]: > >> Thanks for the reply! Yes, as I included in the previous message: >> >> root at spce:/etc/nginx/sites-enabled# ls >> ngcp-panel_admin_api ngcp-panel_csc ngcp-panel_system_api nginx-status >> >> There is no file or directory called nginx in /etc/nginx/sites-enabled/. What you see there is what is in there. Inside /etc/nginx/sites-enabled are: > [...] > > It's about all the files inside the /etc/nginx directory, not a file > named "nginx" inside /etc/nginx/sites-enabled. > > But if there really is no other file referring to port 8081, this is > about the issue that Guillem already pointed you to. quoting from > his mail: > > | This is a known limitation from this prometheus exporter, which fails > | to start if nginx is not running. This has been fixed upstream with > | https://github.com/nginx/nginx-prometheus-exporter/pull/504, so on > | the future NGCP release where we rebase on top of Debian trixie, > | we'll get that new fixed behavior. > > PS: No need to Cc me, I'm subscribed to the mailing list. > > regards > -mika- > > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mprokop at sipwise.com Mon Jan 27 06:32:37 2025 From: mprokop at sipwise.com (Michael Prokop) Date: Mon, 27 Jan 2025 12:32:37 +0100 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <4260F328-6531-49F7-9824-8433B98B4392@gmail.com> References: <2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> <2025-01-22T16-24-09@devnull.michael-prokop.at> <258FE5CF-896D-4682-A62C-6A892FB49E32@gmail.com> <2025-01-27T09-03-31@devnull.michael-prokop.at> <2025-01-27T11-03-37@devnull.michael-prokop.at> <4260F328-6531-49F7-9824-8433B98B4392@gmail.com> Message-ID: <2025-01-27T12-30-39@devnull.michael-prokop.at> * Cesar Mora [Mon Jan 27, 2025 at 07:18:38AM -0400]: > I?m so sorry! My email client keeps messing up the TO address. > > I found a conflict of port 8081 with nginx and tproxy, not sure if this is a part of nginx. > > root at spce:/# grep -Rn "tproxy" /etc/ngcp-config/ > /etc/ngcp-config/templates/etc/services.tt2:339:tproxy 8081/tcp # Transparent Proxy > /etc/ngcp-config/templates/etc/services.tt2:383:#nginx-status [% nginx.status_port %]/tcp # Conflicts with tproxy > /etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.tt2:921: # for BYE, mark whether or not to stop rtproxy > root at spce:/# > > Further digging, I only found 2 references to port 8081 on /etc/nginx/ > > root at spce:~# grep -Rn "8081" /etc/nginx/ > /etc/nginx/sites-enabled/nginx-status:2: listen localhost:8081; > /etc/nginx/sites-available/nginx-status:2: listen localhost:8081; Ok, good and as expected, then. > But I?m guessing the sites-enabled entry is a symlink Yes, and only the files in /etc/nginx/sites-enabled/ matter for nginx in the end. > Other than this, only tproxy refers to 8081 under the config. The tproxy definition in /etc/services (and its template file /etc/ngcp-config/templates/etc/services.tt2) isn't relevant for this. So this applies here: > > But if there really is no other file referring to port 8081, this is > > about the issue that Guillem already pointed you to. quoting from > > his mail: > > > > | This is a known limitation from this prometheus exporter, which fails > > | to start if nginx is not running. This has been fixed upstream with > > | https://github.com/nginx/nginx-prometheus-exporter/pull/504, so on > > | the future NGCP release where we rebase on top of Debian trixie, > > | we'll get that new fixed behavior. regards -mika- From cesarluis89 at gmail.com Mon Jan 27 06:37:31 2025 From: cesarluis89 at gmail.com (Cesar Mora) Date: Mon, 27 Jan 2025 07:37:31 -0400 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <2025-01-27T12-30-39@devnull.michael-prokop.at> References: <2025-01-20T09-58-04@devnull.michael-prokop.at> <280E94AB-BCE0-4BB5-A343-06AABBA17BA9@gmail.com> <2025-01-22T15-45-29@devnull.michael-prokop.at> <2025-01-22T16-24-09@devnull.michael-prokop.at> <258FE5CF-896D-4682-A62C-6A892FB49E32@gmail.com> <2025-01-27T09-03-31@devnull.michael-prokop.at> <2025-01-27T11-03-37@devnull.michael-prokop.at> <4260F328-6531-49F7-9824-8433B98B4392@gmail.com> <2025-01-27T12-30-39@devnull.michael-prokop.at> Message-ID: <85E5BFB7-5B96-4099-8A00-C1BE59CD6E16@gmail.com> I see. So this install is busted then? Having no web UI on restart and manually starting nginx every reboot is not reliable for a production server. I just wonder what causes this on a physical server only, but not on a VM server. Anyways, I?ll see what I can do with a script or something, or migrate the server to a VM? Thanks! > On Jan 27, 2025, at 7:32?AM, Michael Prokop via Spce-user wrote: > > * Cesar Mora [Mon Jan 27, 2025 at 07:18:38AM -0400]: > >> I?m so sorry! My email client keeps messing up the TO address. >> >> I found a conflict of port 8081 with nginx and tproxy, not sure if this is a part of nginx. >> >> root at spce:/# grep -Rn "tproxy" /etc/ngcp-config/ >> /etc/ngcp-config/templates/etc/services.tt2:339:tproxy 8081/tcp # Transparent Proxy >> /etc/ngcp-config/templates/etc/services.tt2:383:#nginx-status [% nginx.status_port %]/tcp # Conflicts with tproxy >> /etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.tt2:921: # for BYE, mark whether or not to stop rtproxy >> root at spce:/# >> >> Further digging, I only found 2 references to port 8081 on /etc/nginx/ >> >> root at spce:~# grep -Rn "8081" /etc/nginx/ >> /etc/nginx/sites-enabled/nginx-status:2: listen localhost:8081; >> /etc/nginx/sites-available/nginx-status:2: listen localhost:8081; > > Ok, good and as expected, then. > >> But I?m guessing the sites-enabled entry is a symlink > > Yes, and only the files in /etc/nginx/sites-enabled/ matter for > nginx in the end. > >> Other than this, only tproxy refers to 8081 under the config. > > The tproxy definition in /etc/services (and its template file > /etc/ngcp-config/templates/etc/services.tt2) isn't relevant for > this. > > So this applies here: > >>> But if there really is no other file referring to port 8081, this is >>> about the issue that Guillem already pointed you to. quoting from >>> his mail: >>> >>> | This is a known limitation from this prometheus exporter, which fails >>> | to start if nginx is not running. This has been fixed upstream with >>> | https://github.com/nginx/nginx-prometheus-exporter/pull/504, so on >>> | the future NGCP release where we rebase on top of Debian trixie, >>> | we'll get that new fixed behavior. > > regards > -mika- > > -- > Spce-user mailing list > Spce-user at lists.sipwise.com > http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mprokop at sipwise.com Mon Jan 27 07:25:17 2025 From: mprokop at sipwise.com (Michael Prokop) Date: Mon, 27 Jan 2025 13:25:17 +0100 Subject: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot In-Reply-To: <85E5BFB7-5B96-4099-8A00-C1BE59CD6E16@gmail.com> References: <2025-01-22T15-45-29@devnull.michael-prokop.at> <2025-01-22T16-24-09@devnull.michael-prokop.at> <258FE5CF-896D-4682-A62C-6A892FB49E32@gmail.com> <2025-01-27T09-03-31@devnull.michael-prokop.at> <2025-01-27T11-03-37@devnull.michael-prokop.at> <4260F328-6531-49F7-9824-8433B98B4392@gmail.com> <2025-01-27T12-30-39@devnull.michael-prokop.at> <85E5BFB7-5B96-4099-8A00-C1BE59CD6E16@gmail.com> Message-ID: <2025-01-27T13-23-14@devnull.michael-prokop.at> Hi, * Cesar Mora [Mon Jan 27, 2025 at 07:37:31AM -0400]: > I see. So this install is busted then? Having no web UI on restart > and manually starting nginx every reboot is not reliable for a > production server. I just wonder what causes this on a physical > server only, but not on a VM server. Anyways, I?ll see what I can > do with a script or something, or migrate the server to a VM? Well, when nginx fails to start after a reboot, is anything else listening on port 8081 already? Check with: ss -tulpnO -o state all '( sport = :8081 )' regards -mika-