-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
level=fatal msg="open /dev/cuaU0: device busy" #9
Comments
Hi, Your device seems used by another process on your machine. You can check that with the command : lsof /dev/cuaU0 |
Thanks but I have allready checked with a |
EDIT : Can you try to compile from source in your openbsd please ? Like this : git clone git@github.com:syberalexis/linky-exporter.git
cd linky-exporter
GOOS=openbsd GOARCH=amd64 VERSION=0.1.3 make clean build
./dist/linky-exporter-0.1.3-openbsd-amd64 EDIT 2 : Sorry, i didn't understand the situation faster ^^ |
HI, Openbsd 7.1 |
Hi, |
Hum, the dependency to use serial port have a PR to support freebsd : https://github.com/tarm/serial/pull/55/files. |
Hi, |
Oh yes, sorry. |
You can find an OpenBSD version in release https://github.com/syberalexis/linky-exporter/releases/tag/v2.1.0 |
Hi, I tried to compile & from binary, I get the same issue: Serial port busy :(
|
Hi, |
Hi, Same issue here in a docker container running on raspberry. I’m running the latest version, my Dockerfile :
I had to comment the USER argument due to permission issue. I’ll try to reproduce with a previous release of linky-exporter |
I’m not reproducing the problem with v2.0.1 |
Hi jude16, Thank you for your testing and review. |
Yes I tried as root too :( |
Hi sachaz, |
hey, As far I know I'm in strandard TIC mode (we asked to Enercoop to active the "advanced mode". I use minicom:
|
Hi, Oh, the exporter doesn't support Standard TIC mode for now. I try to work on it this week or the week after ;) Have a nice week. EDIT: I edit your post to hide your linky id ;) |
Hi, hoooooo okay !maybe add this information in your readme ? |
Hi, Yes, I prepare a better version of the project. |
Hi, |
Hello Yes I think we are only few geeks which read this (https://www.enedis.fr/media/2035/download) Enedis documentation to see that there are 2 modes, historical & standard. French part (because this applies only here):
|
Thanks @hugocollignon it's helpfull for a non-enedis provider request for standard mode. |
Hello, I have a little good news. Can you try this new version and tell me if it's work and send produced metrics please or produced error ^^ To build the new version : git clone git@github.com:syberalexis/linky-exporter.git
cd linky-exporter
git checkout standard-tic-mode Choose the good command to build on your destination environment ;) BUILD_GO111MODULE=on GOOS=openbsd GOARCH=amd64 make clean build OpenBSD armv6 : BUILD_GO111MODULE=on GOOS=openbsd GOARCH=arm GOARM=6 make clean build OpenBSD armv7 : BUILD_GO111MODULE=on GOOS=openbsd GOARCH=arm GOARM=7 make clean build Linux amd64 : BUILD_GO111MODULE=on GOOS=linux GOARCH=amd64 make clean build Linux armv6 : BUILD_GO111MODULE=on GOOS=linux GOARCH=arm GOARM=6 make clean build Linux armv7 : BUILD_GO111MODULE=on GOOS=linux GOARCH=arm GOARM=7 make clean build I will start in few days code comments and refoactoring. Have a nice day. |
Salut syberalexis, Waowww with this winter getting colder this is a good news :) Here are my steps:
then try to build:
There is an error in your variables declaration in the Makefile ? Have a nice day |
Hello sachaz, It’ seems to be make command is different on openbsd than other unix systems. Can you try the command gmake in replacement of make, please. Have a nice evening. |
Hey syberalexis, Sure you are right it's gmake to be used here.
after if I try a minicom/cu on the /dev/cua00 the device is still busy Kind regards |
Hello, Oh sorry, I just remember, I forgot to add parameters to change the mode… Can you pull last version and modify in cmd/linky-exporter/main.go at line 82, the I change main parameters this weekend ;) have a nice day |
Hola, thanks for all your support. Now the daemon is crashing (launched as root for now):
Good day for you too |
Hello, I fix the problem and add mode choice to command. I hope it's good but i write more tests to increase quality. Have a nice day :) |
Hi, here is an output of the daemon after the first curl http://localhost:9101/metrics
|
Hi, Can you try with parameters I work on the auto detect mode and fixed parameters ;) |
cerbere11|18:43:42|:/home/sacha/linky-exporter#dist/linky-exporter--openbsd-amd64 --device /dev/cuaU0 --port=9101 --standard --debug
|
here are the Prometheus outputs:
or
|
Ah good news, it's work pretty well, except linky_load_curve_point ^^ EDIT: I see version label is buggy :/ |
YEY !!! It works fine now ! |
:) Not now for this new exporter metrics. I fixed the autodetect mode too :) |
For OpenBSD people here is a simple daemonize script in
with a
|
Thank you, I will include this into the new version of documentation :) |
Hello, What is your scrape_interval and scrape_timeout in Prometheus config ? If there is an optimization problem, you will can open a new issue ;) |
Hey Let's go to #11 Daemon Optimization :) |
Hello, The new released version of Linky exporter is ready : https://github.com/syberalexis/linky-exporter/releases/tag/v3.0.0 ;) A dashboard is available with id 17649. Have a nice day. |
Hi,
On compiled linky_exporter v2.0.1 on OpenBSD
/usr/local/bin/linky_exporter -d /dev/cuaU0 -p 9101
I got messages like open /dev/cuaU0: device busy
cu or minicom on this device is working
The text was updated successfully, but these errors were encountered: