hardbyte / hardbyte/python-can
can.logger script doesn't work when started from systemd
- Linguagem predominante
- Python
- Estrelas
- 1.6k
- Forks
- 697
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
Hi,
I use a systemd service to log the socketcan can0 with can.logger script.
I use a Unit file that call the script:
...
[Service]
Type=simple
ExecStart=python -m can.logger -f /home/admin/can-logs/test.blf -v -c can0 -i socketcan
...
This script works perfectly when called from the linux shell, but when I start it from the service, the log file is created in /home/admin/can-logs but stay empty.
What could be wrong ? is python-can not able to handle socketcan from systemd service ?
Thanks for your help,
Guia de contribuição
Direção de pesquisa
Start with the systemd Unit and its ExecStart command, then compare its environment and permissions with the working Linux shell invocation. Reproduce the service run with the can.logger command and determine why the created BLF file remains empty; done means logging from can0 produces records under systemd.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- linux, python
- Domínio
- embedded-iot, operating-systems
- Tipo de issue
- Bug
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 25/100