[root@ipfire /]# tail /var/log/messages
Oct 4 19:28:53 ipfire connectd[29425]: No pppd is running. Trying reconnect.
Oct 4 19:28:54 ipfire connectd[29425]: Reconnecting: Attempt 5 of 5
Oct 4 19:28:54 ipfire connectd[29425]: Switched to backup profile 1
Oct 4 19:28:54 ipfire connectd[29425]: Exiting gracefully connectd with PID 29425.
Oct 4 19:28:55 ipfire pppd[29614]: pppd 2.5.0 started by root, uid 0
Oct 4 19:28:55 ipfire pppd[29614]: Can’t create lock file /var/run/pppd/lock/LCK…ttyUSB0: No such file or directory
Oct 4 19:28:55 ipfire pppd[29614]: Exit.
Oct 4 19:28:55 ipfire connectd[29615]: Connectd (start) started with PID 29615
Oct 4 19:28:55 ipfire connectd[29615]: No pppd is running. Trying reconnect.
Oct 4 19:28:56 ipfire connectd[29615]: Reconnecting: Attempt 1 of 5
The same modem/ppp configuration worked ok since version ~163. Did not change a thing.
You may want to work with the Community before going back to 178
The message log above looks like it may be the middle of the reconnect messages. Can you look earlier in the log for the beginning and then look in the area (AND before). Please post those.
Yes, looks like the 2.5.0 update missed changed the lock file and don’t create it if it is not present.
All the people who tested out the 2.5.0 version in CU179 Testing flagged up a few bug issues with the configure settings but the lock file was not one of them. All those people must have setups that aren’t using the lock file.
The ppp devs are working on a 2.5.1 update which is intended to have the fix for this. A Pull Request for the problem has been raised
but it is not yet finalised. There was some talk about making the lock file location configurable via configure but they now will hard code it but to the correct location. The ppp plan is to have the Pull Request (PR) for the patch done by end of this week or so.
Once that is finalised then I can create an IPFire patch from the PR and submit a patch which would end up in Core Update 181 unless version 2.5.1 comes out quickly.
When CU181 Testing comes out it would be good if you can evaluate it to confirm that it works. I can create the update patches but I don’t have any ability to test out a ppp connection. I am running with dhcp from glass fibre via a code converter from optical signals to ethernet signals.
As a workaround it might work for you if you create the /var/run/ppd/lock/ directory because the message seems to be that the directory was not found and ppp does not create it if it is not present.
You can’t. Without internet your only option would be a fresh install of a core update followed by a restore of your IPFire backup but that presumes you already have an iso copy of the installation stored somewhere locally.
That is why I think your best bet is to try out creating the directory that is requested by ppp. If that directory is available then ppp will be able to place its lock file there and it should then start.
One thing I have noticed is that on IPFire the /var/run directory is symlinked to the /run directory.
So you need to create the pppd/lock/ directory in the /rundirectory so you create the directory /run/pppd/lock/.
After creating the directory the permissions of the pppd and lock directories should be 755. I would expect that to be the case but worth checking.
Once the directory is created then rebooting should allow ppp to find it.
What I don’t understand is why your configuration requires the lock file and all the other users who tested the 2.5.0 update did not run into this problem at all.
I’m sorry but I have no way to check at the moment.
This IPFire is at a distance of about 100 kilometers.
I did the actualization in early September.
I didn’t have time to analyze so I converted the lte modem to hilink.
edit:
After converting the lte usb modem to hilink, it began to work, but there was another problem:
IPFire works after reboot
but
after powering off and powering on it doesn’t work (restarting after unplugging, plugging in lte usb modem helps)
Of course they do. The /var/run directory tree is a temporary set as /run is created anew every time a reboot is done.
However it is good news that creating the tree allows ppp to work for you and hopefully @robidoo .
When the fixed package is available then it will be okay as ppp will then use /var/run/lock and that tree is created in the boot sequence.
Until the updated package is available then the best option is to put the commands creating the /ppd/lock directories into a script and place in rc.local, that way they will be recreated when a reboot is carried out.
When the updated package is available then that script can be disposed of.
