matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
3de6a67353
sonic-buildimage/files/build_templates/snmp.service.j2

18 lines
434 B
Plaintext
Raw Normal View History

one image implementation (#215) * Single image * Fix review comments * Update syncd service. Add HW mgmt to Mellanox single image. * Add single image template for Broadcom platform. SKU should be provided during configure: make configure PLATFORM=broadcom SKU=Force10-S6000 * Add single image template for Cavium platform. SKU should be provided during configure: make configure PLATFORM=cavium SKU=AS7512 * Add description to sonic_debian_extension.j2 file.
2017-01-29 13:33:33 -06:00
[Unit]
Description=SNMP container
[snmp.service] Make swss.service a requisite (#2790)
2019-04-16 20:32:36 -05:00
Requires=updategraph.service
Requisite=swss.service
[services] improve startup time by changing startup order (#3656) * [services] improve startup time by given precedence to critical services (syncd.service) Signed-off-by: Stepan Blyschak <stepanb@mellanox.com>
2019-10-31 11:18:26 -05:00
After=updategraph.service swss.service syncd.service
[boot] Refactor: All services which start Docker containers start before ntp-config service (#2335)
2018-12-03 18:01:44 -06:00
Before=ntp-config.service
[services] make snmp.timer work again and delay telemetry.service (#3742) Delay CPU intensive services at boot - How I did it Made snmp.timer work and add telemetry.timer. But this is not enough because it breaks the existing snmp dependency on swss. So, in this solution snmp timer is a wanted by swss service, but since OnBootSec timer expires only once it will not trigger snmp service, so I added line "OnUnitActiveSec=0 sec" which will start snmp service based on the last time it was active. On boot only OnBootSec will expire, on swss start/restarts only second timer will expire immediately and trigger snmp service. However, snmp service will not stop after "systemctl stop snmp" because of the second timer which will always expire when snmp service because unavailable. So there is a conflict which will be handled by systemd if we add "Conflicts=" line to both snmp.service and snmp.timer. So during boot: snmp does not start by default swss starts and starts snmp timer OnUnitActiveSec=0 does not expire since there is no snmp active OnBootSec expires and starts snmp service and snmp timer gets stopped During "systemctl restart swss" snmp stops because of Requisite on swss snmp unblocks snmp timer from running swss starts and starts snmp timer OnUnitActiveSec=0 expires imidiately and start snmp which stops snmp timer During "systemctl stop snmp" stop of snmp service unblocks snmp timer but no one starts the timer so it is not started by "OnUnitActiveSec=0"
2019-12-16 11:07:05 -06:00
Conflicts=snmp.timer
[Services] Restart SNMP service upon unexpected critical process exit. (#3650) Signed-off-by: Yong Zhao <yozhao@microsoft.com>
2019-10-22 16:41:12 -05:00
StartLimitIntervalSec=1200
StartLimitBurst=3
one image implementation (#215) * Single image * Fix review comments * Update syncd service. Add HW mgmt to Mellanox single image. * Add single image template for Broadcom platform. SKU should be provided during configure: make configure PLATFORM=broadcom SKU=Force10-S6000 * Add single image template for Cavium platform. SKU should be provided during configure: make configure PLATFORM=cavium SKU=AS7512 * Add description to sonic_debian_extension.j2 file.
2017-01-29 13:33:33 -06:00
[Service]
[oneimage]: Fix race condition in systemd container services (#421) When Type=simple, systemd will consider the service activated immediately after specified in ExecStart process is started. If there is downstream service depending on the state prepared in ExecStart, there will be race condition. For example, issue #390. In this case, database.service calls database.sh, which calls docker run or docker start -a to start database container. However, systemd considers database.service successfully started at the time database.sh begins, not after docker run finishes. As database.service is consider started, bgp.service can be started. The redis database, which bgp service depends on, might or might not have been started at this time point. To fix this issue (and still keeping the functionality to monitor docker status with systemd), we split the ExecStart process into an ExecStartPre part and an ExecStart part. docker run is splitted into docker run -d then docker attach , while docker start -a is splitted into docker start and then docker attach. In this way, we make sure the downstream services are blocked until container is successfully started.
2017-03-22 15:04:48 -05:00
ExecStartPre=/usr/bin/{{docker_container_name}}.sh start
[services] Services which start containers now use 'docker wait' instead of 'docker attach' (#2661)
2019-03-08 12:59:41 -06:00
ExecStart=/usr/bin/{{docker_container_name}}.sh wait
one image implementation (#215) * Single image * Fix review comments * Update syncd service. Add HW mgmt to Mellanox single image. * Add single image template for Broadcom platform. SKU should be provided during configure: make configure PLATFORM=broadcom SKU=Force10-S6000 * Add single image template for Cavium platform. SKU should be provided during configure: make configure PLATFORM=cavium SKU=AS7512 * Add description to sonic_debian_extension.j2 file.
2017-01-29 13:33:33 -06:00
ExecStop=/usr/bin/{{docker_container_name}}.sh stop
[Services] Restart SNMP service upon unexpected critical process exit. (#3650) Signed-off-by: Yong Zhao <yozhao@microsoft.com>
2019-10-22 16:41:12 -05:00
Restart=always
RestartSec=30
[services] Restart SwSS service upon unexpected critical process exit (#2845) * [service] Restart SwSS Docker container if orchagent exits unexpectedly * Configure systemd to stop restarting swss if it attempts to restart more than 3 times in 20 minutes * Move supervisor-proc-exit-listener script * [docker-dhcp-relay] Enhance wait_for_intf.sh.j2 to utilize STATEDB * Ensure dependent services stop/start/restart with SwSS * Change 'StartLimitInterval' to 'StartLimitIntervalSec', as Stretch installs systemd 232 (>= v230) * Also update journald.conf options * Remove 'PartOf' option from unit files * Add '$(SUPERVISOR_PROC_EXIT_LISTENER_SCRIPT)' to new shared docker-orchagent makefile * Make supervisor-proc-exit-listener script read from 'critical_processes' file inside container * Update critical_processes file for swss container
2019-05-01 10:02:38 -05:00
Reference in New Issue Copy Permalink