I've been running a web application based on www/node14 on FreeBSD and I had written an rc script which would start the application automatically. I recently upgraded my server from FreeBSD 12 to FreeBSD 13 and found that my web application no longer started automatically. The system message showed that
I spent lots of time on fixing this issue. I also checked the release note to see if there is anything that might cause this issue. But, unfortunately I didn't find anything relevant. If I hadn't accidentally stumbled upon that post in the mailing list, I might have looked into a completely wrong direction and wasted more time. Since this did not happen on FreeBSD 12, I wonder what changes have been made to rc in FreeBSD 13 that might have caused this issue. Or how should I find out about changes other than reading the release note? More importantly, how do you sort out upgrade issues like this more efficiently? I do plan to stay on FreeBSD and stay up-to-date so I want to avoid similar things when I upgrade my server to FreeBSD 14, 15, 16, .... (long live FreeBSD!)
ld-elf.so.1: Shared object "libuv.so.1.0.0" not found, required by "node"
. But I did find libuv.so.1.0.0 in /usr/local/lib and I was able to start my web application by running service webapp start
. I tried reinstalling all packages but to no avail. I then found a post in the mailing list (sorry I can't find it anymore) which suggested to add DAEMON
after REQUIRE
in my rc script. After that, my web application starts normally again.I spent lots of time on fixing this issue. I also checked the release note to see if there is anything that might cause this issue. But, unfortunately I didn't find anything relevant. If I hadn't accidentally stumbled upon that post in the mailing list, I might have looked into a completely wrong direction and wasted more time. Since this did not happen on FreeBSD 12, I wonder what changes have been made to rc in FreeBSD 13 that might have caused this issue. Or how should I find out about changes other than reading the release note? More importantly, how do you sort out upgrade issues like this more efficiently? I do plan to stay on FreeBSD and stay up-to-date so I want to avoid similar things when I upgrade my server to FreeBSD 14, 15, 16, .... (long live FreeBSD!)