In D2648, NRPE directory has been set to dirs.share + "/monitoring/checks/nrpe", resolved on FreeBSD to /usr/local/share/monitoring/checks/nrpe directory.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 23 2024
Jul 21 2024
Jan 22 2024
Both naemon-core and naemon-livestatus deployed successfully on WindRiver. Checks run as expected.
Jan 21 2024
Jan 16 2024
May 25 2023
May 24 2023
May 20 2023
As a minimum, to have somewhere (a reports repository?) where we can write those report queries could already be useful, so we don't lose them.
May 18 2023
May 6 2023
May 1 2023
Apr 2 2023
This deployment created the incident:
If one of the two topics lag, we'd have:
$ notification-push --project Nasqueron --group ops --service monitoring --type autoheal.kafka_offset.start --text "Containers sentry_post_process_forwarder_ have an issue. Identified as Kafka offet issue. Starting automatic healing procedure." $ notification-push --project Nasqueron --group ops --service monitoring --type autoheal.kafka_offset.done --text "Containers sentry_post_process_forwarder_ automatic healing one. Containers should be alive."
We don't use uptime anymore.
Mar 30 2023
Mar 28 2023
Mar 25 2023
Looks good to me and seems to work like a charm on sentry.nasqueron.org:
We've an app created according https://develop.sentry.dev/integrations/github/
Test mail received with D2918:
The "could not open panic log" could also mean error also occurs for /srv/exim/sentry_smtp/log
$ docker logs sentry_smtp 10 LOG: MAIN 10 exim 4.92 daemon started: pid=10, no queue runs, listening for SMTP on port 25 (IPv6 and IPv4) 11 LOG: host_lookup_failed MAIN 11 no host name found for IP address 172.18.3.19 11 LOG: MAIN PANIC DIE 11 Failed to create directory "/var/spool/exim4/input": Permission denied 11 11 2023-03-14 23:14:08 1pcDqK-00000B-Rm Failed to create directory "/var/spool/exim4/input": Permission denied 11 11 2023-03-14 23:14:08 1pcDqK-00000B-Rm Failed to create directory "/var/spool/exim4/input": Permission denied 11 11 exim: could not open panic log - aborting: see message(s) above 12 LOG: host_lookup_failed MAIN 12 no host name found for IP address 172.18.3.19 12 LOG: MAIN PANIC DIE 12 Failed to create directory "/var/spool/exim4/input": Permission denied 12 12 2023-03-14 23:15:31 1pcDrf-00000C-5i Failed to create directory "/var/spool/exim4/input": Permission denied 12 12 2023-03-14 23:15:31 1pcDrf-00000C-5i Failed to create directory "/var/spool/exim4/input": Permission denied 12 12 exim: could not open panic log - aborting: see message(s) above 13 LOG: host_lookup_failed MAIN 13 no host name found for IP address 172.18.3.21 13 LOG: MAIN PANIC DIE 13 Failed to create directory "/var/spool/exim4/input": Permission denied 13 13 2023-03-20 12:00:02 1peEBG-00000D-9c Failed to create directory "/var/spool/exim4/input": Permission denied 13 13 2023-03-20 12:00:02 1peEBG-00000D-9c Failed to create directory "/var/spool/exim4/input": Permission denied 13 13 exim: could not open panic log - aborting: see message(s) above
Current status
$ docker pull nasqueron/sentry […] $ sentry nasqueron upgrade […] Running migrations for default Operations to perform: Apply all migrations: admin, auth, contenttypes, nodestore, replays, sentry, sessions, sites, social_auth Running migrations: Applying sentry.0380_backfill_monitor_env_initial... OK Applying sentry.0381_fix_org_slug_casing... OK Applying sentry.0382_add_installation_id_to_service_hook... OK Applying sentry.0383_mv_user_avatar... OK Applying sentry.0384_backfill_installation_ids... OK Applying sentry.0385_service_hook_hc_fk... OK Applying sentry.0386_backfill_monitor_env_checkins... OK Applying sentry.0387_add_until_escalating_column_to_groupsnooze... OK Applying sentry.0388_remove_unique_constraint_artifact_bundle... OK Applying sentry.0389_nullify_debug_id_artifact_bundle_field... OK Applying sentry.0390_remove_field_in_bundle_model... OK Applying sentry.0391_remove_field_in_bundle_model_from_db... OK Applying sentry.0392_add_date_uploaded_field_to_bundle... OK Applying sentry.0393_create_groupforecast_table... OK Applying sentry.0394_set_none_date_uploaded_to_date_added... OK Creating missing DSNs Correcting Group.num_comments counter $ deploy-container sentry […]
Mar 24 2023
$ docker logs sentry_snuba_api 2023-03-24 20:58:44,295 Initializing Snuba... 2023-03-24 20:58:47,701 Snuba initialization took 3.4077668339014053s 2023-03-24 20:58:48,246 Initializing Snuba... 2023-03-24 20:58:51,448 Snuba initialization took 3.2032665936276317s *** Starting uWSGI 2.0.20 (64bit) on [Fri Mar 24 20:58:51 2023] *** compiled with version: 8.3.1 20190311 (Red Hat 8.3.1-3) on 11 November 2021 18:13:24 os: Linux-5.14.0-162.12.1.el9_1.0.2.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Jan 30 22:14:42 UTC 2023 nodename: b225edf80078 machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 8 current working directory: /usr/src/snuba detected binary path: /usr/local/bin/python your memory page size is 4096 bytes detected max file descriptor number: 1073741816 lock engine: pthread robust mutexes thunder lock: enabled uwsgi socket 0 bound to TCP address 0.0.0.0:1218 fd 3 Python version: 3.8.13 (default, Aug 23 2022, 09:42:19) [GCC 10.2.1 20210110] --- Python VM already initialized --- Python main interpreter initialized at 0x564efb872870 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 145808 bytes (142 KB) for 1 cores *** Operational MODE: single process *** initialized 38 metrics spawned uWSGI master process (pid: 1) spawned uWSGI worker 1 (pid: 28, cores: 1) metrics collector thread started 2023-03-24 20:58:51,868 Initializing Snuba... WSGI app 0 (mountpoint='') ready in 4 seconds on interpreter 0x564efb872870 pid: 28 (default app)
ModuleNotFoundError: No module named 'snuba.settings.settings_self_hosted'
$ docker logs sentry_zookeeper […] ===> User uid=0(root) gid=0(root) groups=0(root) ===> Configuring ... ===> Running preflight checks ... ===> Check if /var/lib/zookeeper/data is writable ... ===> Check if /var/lib/zookeeper/log is writable ... ===> Launching ... ===> Launching zookeeper ... [2023-03-24 20:43:14,853] WARN Either no config or no quorum defined in config, running in standalone mode (org.apache.zookeeper.server.quorum.QuorumPeerMain) [2023-03-24 20:43:15,007] WARN o.e.j.s.ServletContextHandler@33f88ab{/,null,STOPPED} contextPath ends with /* (org.eclipse.jetty.server.handler.ContextHandler) [2023-03-24 20:43:15,007] WARN Empty contextPath (org.eclipse.jetty.server.handler.ContextHandler) [2023-03-24 20:43:15,078] WARN ServletContext@o.e.j.s.ServletContextHandler@33f88ab{/,null,STARTING} has uncovered http methods for path: /* (org.eclipse.jetty.security.SecurityHandler)
Mar 16 2023
Mar 15 2023
An issue with the code above is [info errorstack] gives the previous error call stack. It will update when we're done with the error.
Mar 14 2023
A test exception has been sent from Notifications Center to Sentry successfully:
https://sentry.nasqueron.org/organizations/nasqueron/issues/1
Mar 13 2023
Mar 12 2023
Mar 11 2023
Mar 10 2023
Current status
Mar 9 2023
To create the payload, we can use a dictionary: [dict create code "$::errorCode" info "$::errorInfo" stack [info errorstack]].