View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005190 | Taler | deployment and operations | public | 2017-12-05 12:59 | 2021-08-24 14:23 |
| Reporter | Florian Dold | Assigned To | Resolution deadline | ||
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | tweak | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.8 | Fixed in Version | 0.8 | ||
| Summary | 0005190: test, demo and buildbot do not restart on reboot despite cron job | ||||
| Description | We have a @reboot cron job, but for some reason it does not actually start these services. According to the syslog, these jobs *are* executed, but maybe the file system or other services are not ready yet? It looks like buildbot does not have a @reboot cronjob at all. | ||||
| Additional Information | Dec 5 13:19:47 tripwire kernel: [ 19.645407] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Dec 5 13:19:47 tripwire cron[897]: (CRON) INFO (Running @reboot jobs) [...] Dec 5 13:19:48 tripwire CRON[945]: (test-blue) CMD (source $HOME/activate; taler-deployment-restart) Dec 5 13:19:48 tripwire CRON[947]: (demo-blue) CMD (source $HOME/activate; taler-deployment-restart) Dec 5 13:19:48 tripwire CRON[948]: (test-green) CMD (source $HOME/activate; taler-deployment-restart) Dec 5 13:19:48 tripwire CRON[944]: (demo-green) CMD (source $HOME/activate; taler-deployment-restart) | ||||
| Tags | No tags attached. | ||||
| Not sure how to test this! I guess someone should plug a monitor into Tripwire and see what happens on reboot (?) | |
| AFAICT from the last reboot, this is resolved. We don't use cronjobs, but systemd user units, which seem to work well enough. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-12-05 12:59 | Florian Dold | New Issue | |
| 2017-12-05 14:05 | Christian Grothoff | Severity | minor => tweak |
| 2017-12-05 14:05 | Christian Grothoff | Status | new => implementing |
| 2017-12-05 14:05 | Christian Grothoff | Product Version | => git (master) |
| 2017-12-14 14:51 | Christian Grothoff | Target Version | => 0.6 |
| 2018-03-27 09:54 | Marcello Stanisci | Note Added: 0012901 | |
| 2019-01-31 18:40 | Christian Grothoff | Target Version | 0.6 => 0.7.1 |
| 2020-04-11 16:56 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2020-04-11 16:56 | Christian Grothoff | Status | implementing => assigned |
| 2020-04-13 19:40 | Christian Grothoff | Target Version | 0.7.1 => 0.8.1 |
| 2020-07-04 22:09 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2020-07-04 22:09 | Christian Grothoff | Status | assigned => implementing |
| 2020-08-21 15:58 | Florian Dold | Status | implementing => informing |
| 2020-08-21 15:58 | Florian Dold | Resolution | open => fixed |
| 2020-08-21 15:58 | Florian Dold | Note Added: 0016687 | |
| 2020-08-29 12:01 | Christian Grothoff | Fixed in Version | => 0.8 |
| 2020-08-29 12:01 | Christian Grothoff | Target Version | 0.8.1 => 0.8 |
| 2021-08-24 14:23 | Christian Grothoff | Status | informing => closed |