[OK] Composer Version: 2.6.2
[OK] Dependencies up-to-date.
[OK] Database connection successful
[OK] Database Schema is current
[OK] SQL Server meets minimum requirements
[OK] lower_case_table_names is enabled
[OK] MySQL engine is optimal
[OK] Database and column collations are correct
[OK] Database schema correct
[OK] MySQl and PHP time match
[OK] Active pollers found
[OK] Dispatcher Service not detected
[OK] Locks are functional
[OK] Python poller wrapper is polling
[OK] Redis is unavailable
[OK] rrd_dir is writable
[OK] rrdtool version ok
LibreNMS\Cache\Device::get(): Argument #1 ($device) must be of type string|int|null, array given, called in /opt/librenms/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 353 {“userId”:1,“exception”:“[object] (TypeError(code: 0): LibreNMS\Cache\Device::get(): Argument #1 ($device) must be of type string|int|null, array given, called in /opt/librenms/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 353 at /opt/librenms/LibreNMS/Cache/Device.php:69)”}
LibreNMS\Cache\Device::get(): Argument #1 ($device) must be of type string|int|null, array given, called in /opt/librenms/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 353 {“userId”:1,“exception”:“[object] (TypeError(code: 0): LibreNMS\Cache\Device::get(): Argument #1 ($device) must be of type string|int|null, array given, called in /opt/librenms/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 353 at /opt/librenms/LibreNMS/Cache/Device.php:69)”}
I got quiet the same problem, the mail is sent using the test button (from alert → alert transport → orange button) but it is not working/triggering when i associated it in a “Alert Rules” → “transports”
A followup on mine. A Warning level alert did trigger this morning for an environmental device but no Criticals have gone off even when I purposefully powered down a switch. My test transport button also fails with a general error.
i finally make it works, adding the default transport template from docs in a new alert template.
I thought the default template will be apply as default template but not, i have to add it manually.
I have same issue. Happened the same time as OP.
As i understand, people in this thread only checked the situation, when there is custom email transport created and assigned to alert rule?
What about global default mail transport? Should it work after fix?
I have configured only default one, and set it to issue alerts only to admins (general alert settings). Alerts do not come through.
I tested with custom mail transport and indeed it works.
Should i debug my case further? If so what should i check?
There is no errors in librenms.log
Running test-alert.php not giving any apparent errors. There is line added to event log “Issued recovery for rule … to transport ‘mail’” (same for none recovery).
Running test-alert.php shows this lines:
SQL[SELECT transport_id, transport_type, transport_name FROM alert_transports WHERE is_default=true [] 0.5ms]
Reporting disabled by user setting
:: Transport mail => SQL[select * from alert_transports where alert_transports.transport_id is null limit 1 [] 0.55ms]
Why it says “Reporting disabled by user setting” even though default email transport enabled?
So for completion sake I’ve installed LibreNMS on clean test server.
Everything done according to manual page. Apart from this.
Configured mail(smtp) in global settings.
Created default alert rules.
No custom transport created.
No notifications are coming through.
test-alert.php says “No configured transports”.
On my production server there is no indication here. It even adds record to event log “Issued…to transport ‘mail’…”
Adding transport with:
Contact Type: Role
Email:
Role: Admin
Default: Yes
Notifications start to work (on prod too).
Is this new default behavior? If so: should it be reflected in installation/configuration manual?
Previously you didn’t need to create default mail transport, it worked out of the box.
