API tools faq
paste
Advertisement
Tritonio

Assorted info on the "anacron" symlinked to "true" weirdness in Devuan

Tritonio
May 30th, 2022
148
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 55.48 KB | None | 0 0
raw download clone embed print report
  1. Index» Installation» [SOLVED] Local mail issue after upgrading from Beowulf to Chimaera
  2. Pages:1Post reply
  3. #12022-03-04 23:45:18
  4. Marjorie
  5. Member
  6. From: Teignmouth, UK
  7. Registered: 2019-06-09
  8. Posts: 129
  9. Email
  10. I've just upgraded my desktop PC and my mail server from Beowulf to Chimaera following the Devuan guide on how to do this and having checked the Release Notes first.
  11.  
  12. Both upgrades largely went well. The mail server, that was updated over ssh continued running through the update. One omission from the Guide is what to do if you need contrib and non-free as well an main: I did the upgrade with the sources list as described in the guide then repeated with the augmented sources.
  13.  
  14. I did have some small problems with apache php, where 7.4 was installed by the upgrade but 7.3, which wasn't, was the one enabled. This temporarily borked my web server. Also an issue with directory ownership for chrony, where I needed to identify an apparmor config. change that I had missed as I had stayed with my (amended) old Beowulf apparmor config. instead.
  15.  
  16. Unattended upgrades inherits a Debian config, which I needed to correct so that it will install devuan-security upgrades instead.
  17.  
  18. Anyway the problem I still have is with reading my local mail (var/mail/marjorie) on my desktop PC. I use local mail to check any root messages from anacron, unattended upgrades, apt-listchanges, etc.
  19.  
  20. On my mail server I can log in via ssh and then use mutt. Everything works OK, as before.
  21.  
  22. On my desktop PVC I have one of my evolution mail accounts set up to read local mail . This worked fine on Beowulf. On Chimaera I can read the headers but when I try and open a message it complains
  23.  
  24. Unable to retrieve message. Could not lock “/var/mail/marjorie”
  25.  
  26. I get a similar error message when it tries to refresh the folder.
  27.  
  28. If I start mutt then I can see the headers but if I try and open a message it complains
  29.  
  30. Could not create temporary file!
  31.  
  32. I can't see any differences between the relevant directory or file ownership or permissions between the two computers.
  33.  
  34. I'm using postfix as my local mta.
  35.  
  36. Any help in sorting this would be appreciated.
  37.  
  38. Last edited by Marjorie (2022-03-04 23:46:19)
  39.  
  40. Offline
  41.  
  42. Report Quote
  43. #22022-03-06 13:53:20
  44. Marjorie
  45. Member
  46. From: Teignmouth, UK
  47. Registered: 2019-06-09
  48. Posts: 129
  49. Email
  50. The problem with mutt is now solved. The problem with evolution isn't.
  51.  
  52. When displaying or composing emails the most recent version of mutt need to store temporary files in /var/tmp. It used to store them in /tmp, and that is what it still tells you if you look at the man page. On my PC, but not on my mail server the file permissions for /var/tmp were wrong (40755 not 41777). Correcting this solved the problem with mutt.
  53.  
  54. I still have no solution as to why my evolution mail user agent is unable to open my local mbox mail file (/var/mail/[myusername]), reporting a locking error instead.
  55.  
  56. Offline
  57.  
  58. Report Quote
  59. #32022-03-06 18:20:37
  60. Altoid
  61. Member
  62. Registered: 2017-05-07
  63. Posts: 1,037
  64. Email
  65. Hello:
  66.  
  67. Marjorie wrote:
  68. The problem with evolution isn't.
  69.  
  70. You may want to try disabling apparmor temporarily to see if the problem subsists.
  71.  
  72. I also found this post which may have the answer (or some indication) as to how to solve the problem you are having.
  73.  
  74. https://github.com/netblue30/firejail/issues/3478
  75.  
  76. Cheers,
  77.  
  78. A.
  79.  
  80. Offline
  81.  
  82. Report Quote
  83. #42022-03-06 22:19:26
  84. Marjorie
  85. Member
  86. From: Teignmouth, UK
  87. Registered: 2019-06-09
  88. Posts: 129
  89. Email
  90. Hi Altoid. Thanks for the suggestion.
  91.  
  92. I had considered apparmor as a possible cause as I've previously had to modify apparmor profiles that were too restrictive in the past.
  93.  
  94. However I had checked the list of loaded apparmor profiles and they didn't include one for evolution. I also found the github firejail discussion, but again I wasn't using firejail to confine evolution (albeit the firejail profile is loaded).
  95.  
  96. What I hadn't done is actually stop apparmor to check if that was the cause of the problem.
  97. Unfortunately the problem persists even when I stop apparmor.
  98.  
  99. Does anyone have evolution working in Chimaera and it reading their local mbox files OK?
  100. As it did work in evolution in Beowulf (3.30.5-1.1) and it doesn't now in Chimaera ( 3.38.3-1) I wonder if it could be a regression in this version of evolution.
  101. I'm aware there is another problem with this version (syncing with google contact/calendar) that is allegedly fixed in the version in Debian testing ( 3.43.2-2).
  102.  
  103. Last edited by Marjorie (2022-03-06 22:20:28)
  104.  
  105. Offline
  106.  
  107. Report Quote
  108. #52022-03-07 11:05:24
  109. Altoid
  110. Member
  111. Registered: 2017-05-07
  112. Posts: 1,037
  113. Email
  114. Hello:
  115.  
  116. Marjorie wrote:
  117. Thanks ...
  118.  
  119. You're welcome.
  120.  
  121. Marjorie wrote:
  122. ... had considered apparmor as a possible cause ...
  123. ... didn't include one for evolution.
  124. ... wasn't using firejail to confine evolution ...
  125. ... problem persists even when I stop apparmor.
  126.  
  127. I see.
  128.  
  129. From my limited understanding of the problem at hand, there is something (could be a bug) that is not allowing access to your mailbox.
  130. My gut tells me that the issue is like the one that was affecting mutt.
  131.  
  132. Maybe there's something in the /var/log/auth file that could be of use.
  133.  
  134. Is there a log file for evolution you could look at?
  135.  
  136. I've seen that version 3.2.3 has/had a debug setting you can enable to start it from the command line:
  137. See: https://askubuntu.com/questions/301665/ … -a-logfile
  138.  
  139. I do not use apparmor or any of the other 'security' applications like tomoyo that are quietly enabled by default (!) in Linux these days, so my kernel command line includes security=none apparmor=0.
  140.  
  141. You may want to try adding the same stanza at boot time to see if it has any effect as as well as temporarily disabling firejail while you are at it.
  142.  
  143. Hope that helps, can't think of anything else.
  144.  
  145. Best,
  146.  
  147. A.
  148.  
  149. EDIT:
  150.  
  151. It would seem that it's a bug ...
  152.  
  153. https://bugs.debian.org/cgi-bin/bugrepo … 1006603#10
  154.  
  155. ... albeit with a temporary workaround:
  156.  
  157. post #10 wrote:
  158. Probably the same as https://bugs.debian.org/cgi-bin/bugrepo … ug=1004484
  159. which points to the possible problem source and also a temporary solution.
  160.  
  161. Best,
  162.  
  163. A.
  164.  
  165. Last edited by Altoid (2022-03-08 01:14:20)
  166.  
  167. Offline
  168.  
  169. Report Quote
  170. #62022-03-08 20:51:22
  171. Marjorie
  172. Member
  173. From: Teignmouth, UK
  174. Registered: 2019-06-09
  175. Posts: 129
  176. Email
  177. I never did get to the bottom of the inability of Evolution to get a lock on the /var/mail/marjorie Mbox folder after the Chimaera upgrade.
  178.  
  179. However I have solved the problem, by moving my local mail from Mbox to Maildir format and configuring Postfix, Mutt and Evolution to use it. As it stores individual emails in separate files, Maildir doesn't need file locking.
  180.  
  181. As a mail storage solution Mbox is of course obsolete, however it was what was installed, I think by default, when I first installed Ascii and at that point it did work with both Evolution and Mutt without the file locking issues so I never bothered to change it.
  182.  
  183. Converting to Maildir was pretty simple, once I had tracked down how to do it.
  184. However I remain a bit puzzled why the Debian/Devuan installation defaults local mail to use mbox.
  185.  
  186. Last edited by Marjorie (2022-03-08 20:54:04)
  187.  
  188. Index» Devuan» Something strange happens to OpenRC after upgrade to Chimaera
  189. Pages:1Post reply
  190. #12022-02-17 18:03:26
  191. bimon
  192. Member
  193. Registered: 2019-09-09
  194. Posts: 167
  195. Email
  196. I have added echo $PATH manually to the /lib/rc/sh/supervise-daemon.sh
  197.  
  198. root@kube:~# service k3s restart
  199. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/lib/rc/bin/
  200. /lib/rc/sh/supervise-daemon.sh: line 26: ebegin: command not found
  201. /lib/rc/sh/supervise-daemon.sh: line 52: eend: command not found
  202. * ERROR: k3s failed to start
  203.  
  204. root@kube:~# ls /lib/rc/bin/ebegin
  205. /lib/rc/bin/ebegin
  206.  
  207. Also I get a message about missing shell_var (/lib/rc/bin/shell_var) during booting the system.
  208.  
  209. root@kube:~# dpkg -al | grep openrc
  210. ii openrc 0.42-2.1 amd64 dependency based service manager (runlevel change mechanism)
  211.  
  212. Why rc scripts cannot find binaries from /lib/rc/bin/ ?
  213.  
  214. Last edited by bimon (2022-02-17 18:05:00)
  215.  
  216. Offline
  217.  
  218. Report Quote
  219. #22022-02-18 17:09:36
  220. chris2be8
  221. Member
  222. Registered: 2018-08-11
  223. Posts: 138
  224. Run ls -l /lib/rc/bin/ebegin and check if it's marked executable. If it's a symlink to somewhere run ls -l against the destination (repeat until you reach the end if that's a symlink too). Post full output here if you can't understand it.
  225.  
  226. Then run file /lib/rc/bin/ebegin to see what it is. If it's some kind of script look at the first line of it to see which interpreter it's trying to use. And check that exists. Trying to run a script that tries to use an interpreter that does not exist might produce that message.
  227.  
  228. Also look at /lib/rc/sh/supervise-daemon.sh to see if it's changing the path anywhere relevant. And post lines 26 and 52 from it here if you are not sure what they are trying to do.
  229.  
  230. Chris
  231.  
  232. Offline
  233.  
  234. Report Quote
  235. #32022-02-19 23:58:22
  236. bimon
  237. Member
  238. Registered: 2019-09-09
  239. Posts: 167
  240. Email
  241. Thank you very much for trying to help me.
  242.  
  243. root@kube:~# file /lib/rc/bin/ebegin
  244. /lib/rc/bin/ebegin: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=06fede7e085916fa8a23de855fd26a1dbaaf2227, for GNU/Linux 3.2.0, stripped
  245.  
  246. root@kube:~# ls -al /lib/rc/bin/ebegin
  247. -rwxr-xr-x 1 root root 35496 Apr 2 2021 /lib/rc/bin/ebegin
  248. Offline
  249.  
  250. Report Quote
  251. #42022-02-20 00:01:20
  252. bimon
  253. Member
  254. Registered: 2019-09-09
  255. Posts: 167
  256. Email
  257. root@kube:~# head -n 60 /lib/rc/sh/supervise-daemon.sh
  258. # start / stop / status functions for supervise-daemon
  259.  
  260. # Copyright (c) 2016 The OpenRC Authors.
  261. # See the Authors file at the top-level directory of this distribution and
  262. # https://github.com/OpenRC/openrc/blob/master/AUTHORS
  263. #
  264. # This file is part of OpenRC. It is subject to the license terms in
  265. # the LICENSE file found in the top-level directory of this
  266. # distribution and at https://github.com/OpenRC/openrc/blob/master/LICENSE
  267. # This file may not be copied, modified, propagated, or distributed
  268. # except according to the terms contained in the LICENSE file.
  269.  
  270. extra_commands="healthcheck unhealthy ${extra_commands}"
  271.  
  272. supervise_start()
  273. {
  274. if [ -z "$command" ]; then
  275. ewarn "The command variable is undefined."
  276. ewarn "There is nothing for ${name:-$RC_SVCNAME} to start."
  277. return 1
  278. fi
  279.  
  280. ebegin "Starting ${name:-$RC_SVCNAME}"
  281. # The eval call is necessary for cases like:
  282. # command_args="this \"is a\" test"
  283. # to work properly.
  284. eval supervise-daemon "${RC_SVCNAME}" --start \
  285. ${retry:+--retry} $retry \
  286. ${directory:+--chdir} $directory \
  287. ${chroot:+--chroot} $chroot \
  288. ${output_log+--stdout} ${output_log} \
  289. ${error_log+--stderr} $error_log \
  290. ${pidfile:+--pidfile} $pidfile \
  291. ${respawn_delay:+--respawn-delay} $respawn_delay \
  292. ${respawn_max:+--respawn-max} $respawn_max \
  293. ${respawn_period:+--respawn-period} $respawn_period \
  294. ${healthcheck_delay:+--healthcheck-delay} $healthcheck_delay \
  295. ${healthcheck_timer:+--healthcheck-timer} $healthcheck_timer \
  296. ${command_user+--user} $command_user \
  297. ${umask+--umask} $umask \
  298. ${supervise_daemon_args:-${start_stop_daemon_args}} \
  299. $command \
  300. -- $command_args $command_args_foreground
  301. rc=$?
  302. if [ $rc = 0 ]; then
  303. [ -n "${chroot}" ] && service_set_value "chroot" "${chroot}"
  304. [ -n "${pidfile}" ] && service_set_value "pidfile" "${pidfile}"
  305. fi
  306. eend $rc "failed to start ${name:-$RC_SVCNAME}"
  307. }
  308.  
  309. supervise_stop()
  310. {
  311. local startchroot="$(service_get_value "chroot")"
  312. local startpidfile="$(service_get_value "pidfile")"
  313. chroot="${startchroot:-$chroot}"
  314. pidfile="${startpidfile:-$pidfile}"
  315. ebegin "Stopping ${name:-$RC_SVCNAME}"
  316. supervise-daemon "${RC_SVCNAME}" --stop \
  317. ${pidfile:+--pidfile} $chroot$pidfile
  318. Offline
  319.  
  320. Report Quote
  321. #52022-02-20 17:40:24
  322. chris2be8
  323. Member
  324. Registered: 2018-08-11
  325. Posts: 138
  326. I don't have OpenRC on my system so I'm just guessing here.
  327.  
  328. Try reading the man pages for ebegin and eend (if they have them) to see what they should do.
  329. Try calling them directly (passing ebegin a suitable message as a parameter). Do they work?
  330.  
  331. The part of the script you posted defines a function the script will call further on. Does it change the PATH before calling it?
  332.  
  333. Does anyone who has OpenRC installed have any suggestions? Even just to say it works for them.
  334.  
  335. And one last thought, are you on a x86-64 CPU? x86-64 won't work on ARM etc.
  336.  
  337. Chris
  338.  
  339. Offline
  340.  
  341. Report Quote
  342. #62022-02-20 18:10:42
  343. bimon
  344. Member
  345. Registered: 2019-09-09
  346. Posts: 167
  347. Email
  348. chris2be8 wrote:
  349. Does anyone who has OpenRC installed have any suggestions? Even just to say it works for them.
  350.  
  351. And one last thought, are you on a x86-64 CPU? x86-64 won't work on ARM etc.
  352.  
  353. Chris
  354.  
  355. I have another installation of Chimaera where OpenRC works very fine.
  356.  
  357. root@chimaera:~# service k3s restart
  358. * Starting k3s ...
  359. Offline
  360.  
  361. Report Quote
  362. #72022-02-20 18:46:20
  363. Head_on_a_Stick
  364. Member
  365.  
  366. From: London
  367. Registered: 2019-03-24
  368. Posts: 2,297
  369. Email
  370. chris2be8 wrote:
  371. Try reading the man pages for ebegin and eend (if they have them) to see what they should do.
  372.  
  373. They just provide status messages for startup and rc-status.
  374.  
  375. The OP has clearly been modifying their system in various ways because I can't get the k3s service running under OpenRC without changing the source bashism to .. Since they can't be bothered telling us what they have done to either of their systems or even share more information about this k3s service I really can't be bothered digging deeper...
  376.  
  377. To obtain a root shell use su -. Using just su will result in "command not found" messages.
  378.  
  379. Offline
  380.  
  381. Report Quote
  382. #82022-02-20 19:40:03
  383. bimon
  384. Member
  385. Registered: 2019-09-09
  386. Posts: 167
  387. Email
  388. Can you please suggest a light Kubernetes distribution which works fine on Devuan?
  389.  
  390. My experience with k0s on Chimaera is even worse than with k3s sad
  391.  
  392. I just need to learn and experiment and may be use it for a light (not HL) hosting service.
  393.  
  394. Even Minikube looks like a too heavy for me since it requires 2 cores and 2 Gb of RAM which does not fit a small VPS.
  395.  
  396. May be kind ?
  397.  
  398. https://kind.sigs.k8s.io/
  399.  
  400. Last edited by bimon (2022-02-20 19:59:49)
  401.  
  402. Offline
  403.  
  404. Report Quote
  405. #92022-02-21 04:58:01
  406. bimon
  407. Member
  408. Registered: 2019-09-09
  409. Posts: 167
  410. Email
  411. I was able to start k0s on both Beowulf and Chimaera.
  412.  
  413. On both I had to rename networking service to net, not sure if it is wrong for something else, but at least it makes k0s working.
  414.  
  415. cd /etc/init.d; mv networking net
  416.  
  417. rc-update add net
  418.  
  419. On Beowulf I then was able just to issue the command:
  420.  
  421. service k0s start
  422. But on Chimaera I had to use commands:
  423.  
  424. rc-service -s k0scontroller stop
  425. and
  426.  
  427. rc-service -S k0scontroller start
  428. And still get some warning like:
  429.  
  430. root@chimaera:/etc/init.d# rc-service -S k0scontroller start
  431. * Caching service dependencies ... [ ok ]
  432. Configuring network interfaces...warning: vrf: cache v6: cmd '/bin/ip -6 rule show' failed: returned 255 (RTNETLINK answers: Address family not supported by protocol
  433. Dump terminated
  434. )
  435. done.
  436. I have disabled IPv6 on that host.
  437.  
  438. Last edited by bimon (2022-02-23 01:08:13)
  439.  
  440. Offline
  441.  
  442. Report Quote
  443. #102022-02-21 05:00:39
  444. bimon
  445. Member
  446. Registered: 2019-09-09
  447. Posts: 167
  448. Email
  449. Anyway k0s at least starts now:
  450.  
  451. root@chimaera:/# pstree
  452. init─┬─agetty
  453. ├─anacron───run-parts───apt-compat───sleep
  454. ├─containerd-shim─┬─kube-router───9*[{kube-router}]
  455. │ ├─pause
  456. │ └─11*[{containerd-shim}]
  457. ├─containerd-shim─┬─kube-proxy───8*[{kube-proxy}]
  458. │ ├─pause
  459. │ └─11*[{containerd-shim}]
  460. ├─containerd-shim─┬─metrics-server───8*[{metrics-server}]
  461. │ ├─pause
  462. │ └─10*[{containerd-shim}]
  463. ├─containerd-shim─┬─coredns───9*[{coredns}]
  464. │ ├─pause
  465. │ └─10*[{containerd-shim}]
  466. ├─cron
  467. ├─2*[dbus-daemon]
  468. ├─dbus-launch
  469. ├─dhclient───3*[{dhclient}]
  470. ├─elogind-daemon
  471. ├─6*[getty]
  472. ├─jitterentropy-r
  473. ├─matchbox-deskto───16*[{matchbox-deskto}]
  474. ├─qasmixer───14*[{qasmixer}]
  475. ├─sshd───sshd───bash───pstree
  476. ├─supervise-daemo───k0s─┬─containerd───13*[{containerd}]
  477. │ ├─kine───226*[{kine}]
  478. │ ├─kube-apiserver───16*[{kube-apiserver}]
  479. │ ├─kube-controller───13*[{kube-controller}]
  480. │ ├─kube-scheduler───9*[{kube-scheduler}]
  481. │ ├─kubelet───15*[{kubelet}]
  482. │ └─30*[{k0s}]
  483. ├─udevd
  484. └─vncserver─┬─Xtigervnc───12*[{Xtigervnc}]
  485. └─jwm
  486. Offline
  487.  
  488. Report Quote
  489. #112022-02-21 05:23:09
  490. bimon
  491. Member
  492. Registered: 2019-09-09
  493. Posts: 167
  494. Email
  495. Another Chimaera based host with name kube is unfortunately still broken, OpenRC displays already mentioned errors about missing /lib/rc/bin/ files even during boot process and not related to Kubernetes at all.
  496.  
  497. How can I find the reason comparing kube and ice hosts? (both with Chimaera installed on them).
  498. Which areas shell I compare? Btw, debsums do not find any problems with integrity.
  499.  
  500. I used command:
  501.  
  502. wajig integrity
  503. for the verification.
  504.  
  505. Last edited by bimon (2022-02-21 05:24:32)
  506.  
  507. Offline
  508.  
  509. Report Quote
  510. #122022-02-21 17:01:31
  511. chris2be8
  512. Member
  513. Registered: 2018-08-11
  514. Posts: 138
  515. Check running ebegin and eend manually work. Then call them from a small dummy script as a double check.
  516.  
  517. Look at /lib/rc/sh/supervise-daemon.sh to see if it's changing the PATH anywhere relevant.
  518. Temporarily add echo $PATH to it just before it calls ebegin. Compare with what you get by adding echo $PATH to the start of the script.
  519. If PATH gets changed then work out where it gets changed by adding echo $PATH at suitable places.
  520.  
  521. If all else fails post the whole of the original version of /lib/rc/sh/supervise-daemon.sh here to let someone who knows shell scripting look at it.
  522.  
  523. Chris
  524.  
  525. Offline
  526.  
  527. Report Quote
  528. #132022-02-22 02:27:58
  529. zapper
  530. Member
  531. Registered: 2017-05-29
  532. Posts: 432
  533. Email
  534. I was going to say never had a problem with openrc before even when Chimaera came out, but I just read more carefully...
  535.  
  536. wink
  537.  
  538.  
  539. But anyways...
  540.  
  541. I wonder what changed since Beowulf to cause such an issue to the op...
  542.  
  543. Hmm...
  544.  
  545. Aka:
  546.  
  547. Kubernetes
  548.  
  549. Btw, never used the light version or the other one.
  550.  
  551. Also, looked it up, not sure what would be a good replacement even looking it up on wikipedia.org...
  552.  
  553. Last edited by zapper (2022-02-22 02:30:56)
  554.  
  555. Black Lives Matter! I am white, but I prefer equality over hatred.
  556. Haughtiness comes before a fall, pride before destruction.
  557. Peace be with you!
  558. No one can serve two masters. Either you will hate the one and love the other, or you will be devoted to the one and despise the other. You cannot serve both God and mammon!
  559.  
  560. Offline
  561.  
  562. Report Quote
  563. #142022-02-23 01:19:18
  564. bimon
  565. Member
  566. Registered: 2019-09-09
  567. Posts: 167
  568. Email
  569. I have tried a simple test script:
  570.  
  571. root@kube:/download# cat test.sh
  572. export set PATH=$PATH:/lib/rc/bin;
  573. echo $PATH;
  574. ebegin hello
  575. eend hello
  576.  
  577. root@kube:/download# sh test.sh
  578. /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/lib/rc/bin
  579. * hello ...
  580. * hello
  581. Some more tests on problematic host kube:
  582.  
  583. root@kube:/etc/init.d# /etc/init.d/k0scontroller restart
  584. * Caching service dependencies ...
  585. /lib/rc/sh/rc-functions.sh: line 117: shell_var: command not found
  586. * Found a solvable dependency loop: mountall-bootclean.sh p> mountall-bootclean u> zfs-import a> checkfs n> mountall.sh p> mountall n> mountall-bootclean.sh.
  587. * Solving the loop by breaking mountall-bootclean u> zfs-import.
  588. * Found a solvable dependency loop: mountall.sh p> mountall u> zfs-import a> checkfs n> mountall.sh.
  589. * Solving the loop by breaking mountall u> zfs-import. [ ok ]
  590. Starting hot-plug events dispatcher: udevd1 ... (warning).
  591. Waiting 15 seconds and trying to continue anyway ... (warning).
  592. Synthesizing the initial hotplug events (subsystems)...done.
  593. Synthesizing the initial hotplug events (devices)...done.
  594. Waiting for /dev to be fully populated...done.
  595. Starting boot logger: bootlogdActivating swap...done.
  596. Checking file systems...setterm: terminal xterm-256color does not support --msg
  597. setterm: terminal xterm-256color does not support --msg
  598. done.
  599. Cleaning up temporary files... /tmp.
  600. Mounting local filesystems...done.
  601. Activating swapfile swap, if any...done.
  602. Cleaning up temporary files....
  603. Configuring network interfaces...done.
  604. So: /lib/rc/sh/rc-functions.sh: line 117: shell_var: command not found
  605.  
  606. Continuation of the execution is in the next code fragment, please pay your attention to the "system which openrc did not boot."
  607.  
  608. Actually I had some problems with OpenRC after upgrade, I even could not boot to any run-level, only to something like Ctrl-D (is it level 1?). So I had to install sysv-rc at first, reboot and then reinstall OpenRC once again.
  609.  
  610. But after second install debsums integrity check passes fine, does not it mean all files installed correctly? Then why I still have no OpenRC from the point of view of k0s for example? It seems like it is not completely working OpenRC, even during boot it displays an error about something like above:
  611.  
  612. /lib/rc/sh/rc-functions.sh: line 117: shell_var: command not found
  613.  
  614. * You are attempting to run an openrc service on a
  615. * system which openrc did not boot.
  616. * You may be inside a chroot or you may have used
  617. * another initialization system to boot this system.
  618. * In this situation, you will get unpredictable results!
  619. * If you really want to do this, issue the following command:
  620. * touch /run/openrc/softlevel
  621. * ERROR: k0scontroller failed to start
  622. Last edited by bimon (2022-02-23 01:27:56)
  623.  
  624. Offline
  625.  
  626. Report Quote
  627. #152022-02-23 01:48:10
  628. bimon
  629. Member
  630. Registered: 2019-09-09
  631. Posts: 167
  632. Email
  633. I have added echo $PATH before shell_var command:
  634.  
  635. root@kube:/download# service k0scontroller restart
  636. * Caching service dependencies ...
  637. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  638. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  639. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  640. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  641. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  642. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  643. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  644. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  645. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  646. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  647. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  648. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  649. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  650. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  651. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  652. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  653. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  654. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  655. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  656. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  657. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  658. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  659. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  660. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  661. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  662. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  663. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  664. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  665. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  666. /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  667. /lib/rc/sh/rc-functions.sh: line 118: shell_var: command not found
  668. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  669. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  670. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  671. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  672. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  673. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  674. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  675. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  676. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  677. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  678. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  679. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  680. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  681. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  682. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  683. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  684. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  685. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  686. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  687. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  688. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  689. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  690. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  691. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  692. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  693. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  694. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  695. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  696. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  697. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  698. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  699. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  700. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  701. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  702. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  703. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  704. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  705. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  706. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  707. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  708. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  709. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  710. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  711. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  712. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  713. /lib/rc/sbin:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
  714. * Found a solvable dependency loop: mountall-bootclean.sh p> mountall-bootclean u> zfs-import a> checkfs n> mountall.sh p> mountall n> mountall-bootclean.sh.
  715. * Solving the loop by breaking mountall-bootclean u> zfs-import.
  716. * Found a solvable dependency loop: mountall.sh p> mountall u> zfs-import a> checkfs n> mountall.sh.
  717. * Solving the loop by breaking mountall u> zfs-import. [ ok ]
  718. * You are attempting to run an openrc service on a
  719. * system which openrc did not boot.
  720. * You may be inside a chroot or you may have used
  721. * another initialization system to boot this system.
  722. * In this situation, you will get unpredictable results!
  723. * If you really want to do this, issue the following command:
  724. * touch /run/openrc/softlevel
  725. * ERROR: k0scontroller failed to start
  726.  
  727. As you can see above one call for some reason missed the path:
  728.  
  729. /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  730. /lib/rc/sh/rc-functions.sh: line 118: shell_var: command not found
  731. Last edited by bimon (2022-02-23 01:48:50)
  732.  
  733. Offline
  734.  
  735. Report Quote
  736. #162022-02-23 02:18:49
  737. bimon
  738. Member
  739. Registered: 2019-09-09
  740. Posts: 167
  741. Email
  742. Well, I have uninstalled some service like SafeNET cryptography and now the problem seems to disappear.
  743.  
  744. On the other hand it worked in the previous version of Devuan Beowulf from which I have upgraded this host.
  745.  
  746. Actually there were many warnings displayed about something wrong in SafeNET service LSB specifications even on Beowulf, but at least it worked ...
  747.  
  748. The SafeNET software is obsolete about 5-10 years old.
  749.  
  750. Last edited by bimon (2022-02-23 02:19:46)
  751.  
  752. Index» Installation» [SOLVED] Permissions for script in cron
  753. Pages:Previous 1 2 3
  754. #512021-04-01 13:32:24
  755. ralph.ronnquist
  756. Administrator
  757. From: Clifton Hill, Victoria, AUS
  758. Registered: 2016-11-30
  759. Posts: 690
  760. Once done, how should I test that everything is working properly?
  761.  
  762. One confirmation would be that your fstrim logging shows up.
  763.  
  764. A manual forced test would be like before, i.e. if live-config is uninstalled, then
  765.  
  766. sudo /usr/sbin/anacron -s -d -n -f
  767. should be telling about running the cron.{daily,weekly,monthly} jobs.
  768.  
  769. Offline
  770.  
  771. #522021-04-01 13:56:31
  772. Altoid
  773. Member
  774. Registered: 2017-05-07
  775. Posts: 1,045
  776. Hello:
  777.  
  778. ralph.ronnquist wrote:
  779. One confirmation would be that your fstrim logging shows up.
  780. ... manual forced test would be like before, i.e. if live-config is uninstalled, then ...
  781.  
  782. sudo /usr/sbin/anacron -s -d -n -f
  783. ... should be telling about running the cron.{daily,weekly,monthly} jobs.
  784.  
  785. Right.
  786.  
  787. I'll do all that and report back, hopefully marking this long thread as [Solved].
  788.  
  789. ----
  790. Edit:
  791. Done.
  792. No more /usr/sbin/anacron --> /bin/true
  793.  
  794. groucho@devuan:~$ ls -l /usr/sbin/anacron.orig.anacron
  795. -rwxr-xr-x 1 root root 34832 May 19 2019 /usr/sbin/anacron.orig.anacron
  796. groucho@devuan:~$
  797. groucho@devuan:~$
  798. dpkg -S anacron.orig.anacron
  799. diversion by live-config from: /usr/sbin/anacron
  800. diversion by live-config to: /usr/sbin/anacron.orig.anacron
  801. groucho@devuan:~$
  802. groucho@devuan:~$ ls -l /usr/sbin/anacron
  803. lrwxrwxrwx 1 root root 20 Apr 1 11:06 /usr/sbin/anacron -> anacron.orig.anacron
  804. groucho@devuan:~$
  805. groucho@devuan:~$ dpkg -S /usr/sbin/anacron
  806. diversion by live-config from: /usr/sbin/anacron
  807. diversion by live-config to: /usr/sbin/anacron.orig.anacron
  808. anacron: /usr/sbin/anacron
  809. groucho@devuan:~$
  810. I have purged it but I see that the diversion by live-config is still there.
  811. How to go back to the 'original' pre-live-config configuration?
  812.  
  813. It seems to be working. 8^D!
  814.  
  815. groucho@devuan:~$
  816. groucho@devuan:~$ sudo /usr/sbin/anacron -s -d -n -f
  817. [sudo] password for groucho:
  818. Anacron 2.3 started on 2021-04-01
  819. Job `cron.daily' locked by another anacron - skipping
  820. Job `cron.weekly' locked by another anacron - skipping
  821. Job `cron.monthly' locked by another anacron - skipping
  822. Normal exit (0 jobs run)
  823. groucho@devuan:~$
  824. groucho@devuan:~$
  825. ----
  826.  
  827. Once done, who/where would I have to report this problem to?
  828.  
  829. Does not seem to originate inrefractainstaller-base, more like in the required live-config.
  830. Or is it related to the bug report I linked to?
  831.  
  832. Don't think is would be a good thing just to leave it be. (?)
  833.  
  834. Thank you very much for the time and effort you put into solving this problem for me.
  835. Really appreciate it.
  836.  
  837. Best,
  838.  
  839. A.
  840.  
  841. Last edited by Altoid (2021-04-01 14:34:40)
  842.  
  843. Offline
  844.  
  845. #532021-04-01 15:48:54
  846. fsmithred
  847. Administrator
  848.  
  849. Registered: 2016-11-25
  850. Posts: 2,068
  851. uh-oh...
  852.  
  853. I haven't been paying close attention to this thread.
  854.  
  855. live-config messes with anacron via the live-config script, /lib/live/config/1110-anacron which uses dpkg-divert to disable anacron. This is useful in a live-CD where everything is read-only.
  856. This only activates when you boot into a live system, not an installed system.
  857.  
  858. Refractainstaller copies the RUNNING live system to hard drive.
  859.  
  860. You just uncovered a 10-year-old bug that I didn't know about. The installer needs to undo this during the installation.
  861.  
  862. I suspect that the right way to undo it is to use dpkg-divert.
  863.  
  864. # ls -l /usr/sbin/anacron*
  865. lrwxrwxrwx 1 root root 9 Apr 2 2018 /usr/sbin/anacron -> /bin/true
  866. -rwxr-xr-x 1 root root 38928 Feb 6 14:18 /usr/sbin/anacron.orig.anacron
  867.  
  868. # dpkg-divert --remove /usr/sbin/anacron
  869. dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
  870. Removing 'diversion of /usr/sbin/anacron to /usr/sbin/anacron.orig.anacron by live-config'
  871. And then to verify that it really did what it was supposed to do (but did not):
  872.  
  873. # ls -l /usr/sbin/anacron*
  874. lrwxrwxrwx 1 root root 9 Apr 2 2018 /usr/sbin/anacron -> /bin/true
  875. -rwxr-xr-x 1 root root 38928 Feb 6 14:18 /usr/sbin/anacron.orig.anacron
  876. Yet dpkg-divert thinks it did the right thing:
  877.  
  878. # dpkg-divert --remove /usr/sbin/anacron
  879. dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
  880. No diversion 'any diversion of /usr/sbin/anacron', none removed.
  881. Computer, do as I say!
  882.  
  883. # mv /usr/sbin/anacron.orig.anacron /usr/sbin/anacron
  884. # ls -l /usr/sbin/anacron*
  885. -rwxr-xr-x 1 root root 38928 Feb 6 14:18 /usr/sbin/anacron
  886. root@nomad:/home/phred#
  887. I'll reboot and see what happens.
  888.  
  889. Update: I see this in syslog for the first time after reboot. I think it's working now.
  890.  
  891. Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.daily' in 5 min.
  892. Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.weekly' in 10 min.
  893. Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.monthly' in 15 min.
  894. Offline
  895.  
  896. #542021-04-01 19:54:43
  897. Altoid
  898. Member
  899. Registered: 2017-05-07
  900. Posts: 1,045
  901. Hello:
  902.  
  903. fsmithred wrote:
  904. uh-oh...
  905. I haven't been paying close attention to this thread.
  906.  
  907. Tsk, tsk ... 8^D!!!
  908.  
  909. Can't do everyhting.
  910.  
  911. fsmithred wrote:
  912. live-config messes with anacron via the live-config script ...
  913.  
  914. So it seems.
  915.  
  916. fsmithred wrote:
  917. ... useful in a live-CD where everything is read-only.
  918. ... only activates when you boot into a live system, not an installed system.
  919.  
  920. Yes.
  921.  
  922. fsmithred wrote:
  923. Refractainstaller copies the RUNNING live system to hard drive.
  924.  
  925. The post at Dev1 that I linked to, which had the same /usr/sbin/anacron --> /bin/true and deviations apparently was not/had not been using Refractainstaller.
  926.  
  927. So something other used live-config and generated the same problem.
  928. https://dev1galaxy.org/viewtopic.php?id=1901
  929.  
  930. ie: this would not be specific to the refractainstaller but to how live-config is used by any application. (?)
  931.  
  932. fsmithred wrote:
  933. You just uncovered a 10-year-old bug ...
  934.  
  935. No.
  936.  
  937. It was ralph.ronnquist who saw it and pointed it out to me while helping me sort out the problem I was having with anacron.
  938. https://dev1galaxy.org/viewtopic.php?pid=28663#p28663
  939. I just observed and tried to pay attention.
  940.  
  941. A question just occurred to me: in 10 years, no one else using refractainstaller had a problem/issue with anacron?
  942. Maybe there's something that's not working right.
  943.  
  944. ie:
  945. I realised what was going on when I saw that my fstrim script was not logging.
  946. If not for that, I would have never known about what was going on with anacron.
  947. And I don't recall any system notifications warning me of anacron failures.
  948.  
  949. Not good, no?
  950.  
  951. fsmithred wrote:
  952. The installer needs to undo this during the installation.
  953.  
  954. Sure.
  955.  
  956. But it is live-config that is making a signifficant change.
  957. No clean-up after use?
  958. A notification of some sort?
  959.  
  960. eg:
  961.  
  962. Don't forget to clean up /usr/sbin/anacron --> /bin/true afterwards.
  963.  
  964. fsmithred wrote:
  965. I see this in syslog for the first time after reboot.
  966. ... it's working now.
  967.  
  968. Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.daily' in 5 min.
  969. Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.weekly' in 10 min.
  970. Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.monthly' in 15 min.
  971. Yes, it's working.
  972.  
  973. Thanks a lot for your input.
  974.  
  975. Best,
  976.  
  977. A.
  978.  
  979. Last edited by Altoid (2021-04-01 19:59:11)
  980.  
  981. Offline
  982.  
  983. #552021-04-02 09:44:55
  984. fsmithred
  985. Administrator
  986.  
  987. Registered: 2016-11-25
  988. Posts: 2,068
  989. The post at Dev1 that I linked to, which had the same /usr/sbin/anacron --> /bin/true and deviations apparently was not/had not been using Refractainstaller.
  990.  
  991. So something other used live-config and generated the same problem.
  992. https://dev1galaxy.org/viewtopic.php?id=1901
  993.  
  994. That was a miyolinux system, which uses refractainstaller.
  995.  
  996. The way it's designed, the live-config change should not need to be undone as it only exists in the running live system. If you mount the filesystem inside the live-iso to look at it when it's not running, you would find that the diverted file does not exist. It gets created by live-config when the system boots.
  997.  
  998. Offline
  999.  
  1000. #562021-04-02 10:42:56
  1001. Altoid
  1002. Member
  1003. Registered: 2017-05-07
  1004. Posts: 1,045
  1005. Hello:
  1006.  
  1007. fsmithred wrote:
  1008. That was a miyolinux system ...
  1009.  
  1010. Indeed ...
  1011.  
  1012. GNUser wrote:
  1013. I did not install any live-config packages, so they must have come with Miyo.
  1014.  
  1015. The poster was right.
  1016. I didn't now about refractainstaller being used by Miyo.
  1017.  
  1018. fsmithred wrote:
  1019. ... the live-config change should not need to be undone as it only exists in the running live system.
  1020.  
  1021. Now it's fixed.
  1022.  
  1023. Thanks for your input.
  1024.  
  1025. Best,
  1026.  
  1027. A.
  1028.  
  1029. Index» Hardware & System Configuration» anacron not working in ascii [SOLVED]
  1030. Pages:1Post reply
  1031. #12018-02-24 06:17:03
  1032. GNUser
  1033. Member
  1034.  
  1035. Registered: 2017-03-16
  1036. Posts: 535
  1037. Email
  1038. Anacron is not running on my laptop, regardless of whether it is plugged in or not.
  1039.  
  1040. Here is my /etc/anacrontab (it is the same as on my Devuan Jessie partition):
  1041.  
  1042. # /etc/anacrontab: configuration file for anacron
  1043.  
  1044. # See anacron(8) and anacrontab(5) for details.
  1045.  
  1046. SHELL=/bin/sh
  1047. PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
  1048. HOME=/root
  1049. LOGNAME=root
  1050.  
  1051. # These replace cron's entries
  1052. 1 5 cron.daily run-parts --report /etc/cron.daily
  1053. 7 10 cron.weekly run-parts --report /etc/cron.weekly
  1054. @monthly 15 cron.monthly run-parts --report /etc/cron.monthly
  1055.  
  1056. # bruno
  1057. 7 1 maintenance /opt/scripts/jobs-maintenance
  1058. Here is /etc/default/anacrontab:
  1059.  
  1060. # If set to "yes", start anacron even when on battery power. By
  1061. # default, the /etc/init.d/anacron script tries to avoid running
  1062. # anacron unless on AC power, so as to avoid running down the battery.
  1063. # (Things like the locate updatedb cause a lot of I/O.)
  1064.  
  1065. ANACRON_RUN_ON_BATTERY_POWER=yes
  1066. I already did this, too (I had to do it in Jessie in order for anacron to run while on battery power):
  1067.  
  1068. $ sudo chmod a-x /usr/lib/pm-utils/power.d/anacron
  1069. Looking at /var/log/syslog shows no entries by anacron. Also, /var/spool/anacron is an empty directory with no timestamps. I've tried rebooting and resuming from suspend, both on AC and battery power, and anacron gives no signs of life.
  1070.  
  1071. I have the 2.3-24 version installed. I also tried uninstalling it and installing the 2.3-23 version from Devuan Jessie and it made no difference.
  1072.  
  1073. Any ideas? Anacron is mission-critical for me.
  1074.  
  1075. Last edited by GNUser (2018-02-24 17:55:32)
  1076.  
  1077. Offline
  1078.  
  1079. Report Quote
  1080. #22018-02-24 06:40:03
  1081. GNUser
  1082. Member
  1083.  
  1084. Registered: 2017-03-16
  1085. Posts: 535
  1086. Email
  1087. After much snooping around, I discovered that /usr/sbin/anacron was a link to /bin/true (???)
  1088. The anacron package actually installs /usr/sbin/anacron.orig.anacron (???)
  1089. This fixed the issue: sudo ln -fs /usr/sbin/anacron.orig.anacron /usr/sbin/anacron
  1090.  
  1091. Very, very strange.
  1092.  
  1093. Offline
  1094.  
  1095. Report Quote
  1096. #32018-02-24 14:31:01
  1097. fsmithred
  1098. Administrator
  1099.  
  1100. Registered: 2016-11-25
  1101. Posts: 2,064
  1102. Email
  1103. I just checked one of my ascii installs, and /usr/sbin/anacron is a real file. There are entries in /var/log/syslog, and it looks like it runs when I boot the VM. My anacrontab looks like yours, there are files in /var/spool/anacron for cron.daily .weekly and .monthly with timestamps that match what syslog shows. And my /etc/default/anacron says "No".
  1104.  
  1105. 'apt-file find /usr/sbin/anacron.orig.anacron' turned up nothing. Maybe dpkg -S would show something on your end. Or 'grep anacron /root/.history' to see if you did something and forgot about it.
  1106.  
  1107. Offline
  1108.  
  1109. Report Quote
  1110. #42018-02-24 15:19:44
  1111. GNUser
  1112. Member
  1113.  
  1114. Registered: 2017-03-16
  1115. Posts: 535
  1116. Email
  1117. Thank you for the suggestions, fsmithred.
  1118.  
  1119. I have begun solving the mystery:
  1120.  
  1121. bruno@thinkpad:~$ dpkg -S anacron.orig.anacron
  1122. diversion by live-config from: /usr/sbin/anacron
  1123. diversion by live-config to: /usr/sbin/anacron.orig.anacron
  1124.  
  1125. bruno@thinkpad:~$ dpkg -l | grep live-config
  1126. ii live-config 5.20170112+deb9u1 all Live System Configuration Components
  1127. ii live-config-doc 5.20170112+deb9u1 all Live System Configuration Components (documentation)
  1128. ii live-config-sysvinit 5.20170112+deb9u1 all Live System Configuration Components (sysvinit backend)
  1129. I did not install any live-config packages, so they must have come with Miyo. I will try uninstalling live-config* and reinstalling anacron.
  1130.  
  1131. Offline
  1132.  
  1133. Report Quote
  1134. #52018-02-24 15:29:38
  1135. GNUser
  1136. Member
  1137.  
  1138. Registered: 2017-03-16
  1139. Posts: 535
  1140. Email
  1141. No luck. I purged all three live-config packages and ancron, rebooted, and reinstalled anacron. Similar shenanigans (at least now the symlink is pointing to something sensible and not /bin/true):
  1142.  
  1143. bruno@thinkpad:~$ ls -l /usr/sbin/anacron
  1144. lrwxrwxrwx 1 root root 30 Feb 24 01:36 /usr/sbin/anacron -> /usr/sbin/anacron.orig.anacron
  1145. bruno@thinkpad:~$ dpkg -S anacron.orig.anacron
  1146. diversion by live-config from: /usr/sbin/anacron
  1147. diversion by live-config to: /usr/sbin/anacron.orig.anacron
  1148. This is my /etc/apt/sources.list:
  1149.  
  1150. deb http://pkgmaster.devuan.org/merged/ ascii main
  1151. deb http://pkgmaster.devuan.org/merged/ ascii-security main
  1152. deb http://pkgmaster.devuan.org/merged/ ascii-updates main
  1153. fsmithred, are you sure that your /usr/sbin/anacron is a real file and not a link? If you are sure, what am I missing?
  1154.  
  1155. What is this live-config business anyway? Can I get rid of it?
  1156.  
  1157. Last edited by GNUser (2018-02-24 15:30:49)
  1158.  
  1159. Offline
  1160.  
  1161. Report Quote
  1162. #62018-02-24 17:54:40
  1163. GNUser
  1164. Member
  1165.  
  1166. Registered: 2017-03-16
  1167. Posts: 535
  1168. Email
  1169. I got it. Even after uninstalling the live-config* packages, the diversion that it created continues to live in dpkg, so one has to manually remove the diversion:
  1170.  
  1171. root@thinkpad:/home/bruno# dpkg-divert --list | grep anacron
  1172. diversion of /usr/sbin/anacron to /usr/sbin/anacron.orig.anacron by live-config
  1173.  
  1174. root@thinkpad:/home/bruno# dpkg-divert --remove /usr/sbin/anacron
  1175.  
  1176. root@thinkpad:/home/bruno# dpkg-divert --list | grep anacron
  1177. # no hits
  1178. Now I reinstall anacron and /usr/sbin/anacron is a real file as expected smile
  1179.  
  1180. Last edited by GNUser (2018-02-24 17:56:23)
  1181.  
  1182. /usr/sbin/anacron is a symlink to true
  1183. Bug #1254614 reported by Shalom Crown on 2013-11-25
  1184. 10
  1185. This bug affects 2 people
  1186. Affects Status Importance Assigned to Milestone
  1187. anacron (Ubuntu) Confirmed Undecided Unassigned
  1188. Bug Description
  1189. The original is present in /usr/sbin/anacron.distrib
  1190. Even when I change it , it changes back the next day during / after the anacron daily.
  1191.  
  1192. This is seen on 3 machines. They are all running Lubuntu live images, from USB DOKs, with casper-rw as a separate partition (not file).
  1193.  
  1194. On properly installed machines (mainly Xubuntu) there is no problem.
  1195.  
  1196. transspot@lubuntu:~$ ll /usr/sbin/anac*
  1197. lrwxrwxrwx 1 root root 9 Nov 19 12:54 /usr/sbin/anacron -> /bin/true*
  1198. -rwxr-xr-x 1 root root 30076 Dec 20 2012 /usr/sbin/anacron.distrib*
  1199.  
  1200. transspot@lubuntu:~$ cat /etc/lsb-release
  1201. DISTRIB_ID=Ubuntu
  1202. DISTRIB_RELEASE=13.10
  1203. DISTRIB_CODENAME=saucy
  1204. DISTRIB_DESCRIPTION="Ubuntu 13.10"
  1205.  
  1206. ProblemType: Bug
  1207. DistroRelease: Ubuntu 13.10
  1208. Package: anacron 2.3-19ubuntu2
  1209. ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  1210. Uname: Linux 3.11.0-12-generic i686
  1211. ApportVersion: 2.12.5-0ubuntu2.1
  1212. Architecture: i386
  1213. CasperVersion: 1.336ubuntu1
  1214. Date: Mon Nov 25 09:29:30 2013
  1215. LiveMediaBuild: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  1216. MarkForUpload: True
  1217. ProcEnviron:
  1218. TERM=xterm
  1219. PATH=(custom, no user)
  1220. XDG_RUNTIME_DIR=<set>
  1221. LANG=en_US.UTF-8
  1222. SHELL=/bin/bash
  1223. SourcePackage: anacron
  1224. UpgradeStatus: No upgrade log present (probably fresh install)
  1225.  
  1226. Tags: apport-bug i386 saucy
  1227. Shalom Crown (shalom-crown) wrote on 2013-11-25: #1
  1228. Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
  1229. Launchpad Janitor (janitor) wrote on 2014-11-09: #2
  1230. Status changed to 'Confirmed' because the bug affects multiple users.
  1231.  
  1232. Changed in anacron (Ubuntu):
  1233. status: New → Confirmed
  1234. Uwe Lück (uwe-lueck) wrote on 2014-11-09: #3
  1235. I have spent many days with learning about logrotate, cron jobs, and launchpad etiquette (as to posting a comment), which may take me into financial troubles. Now just let me …
  1236.  
  1237. I discovered this here starting from bug #1385537, and it helped me to fix the latter. However, I have described there how my situation differs from the situation here.
  1238.  
  1239. Another point: I have wondered and searched the web much time in order not only to find out how rotating logs and anacron etc. work, but actually: whether the developers of (Lu|Xu|U)buntu have *intended* to rotate logs by anacron.
  1240.  
  1241. Idea from that: Cron jobs might *intentionally* have been disabled (by linking to /bin/true) for a *live* session, maybe not thinking about the persistent case, rather about brief rescue or installation sessions where rotating and cron jobs seem to be useless and perhaps disturb jobs the user has in mind.
  1242.  
  1243. Index» Hardware & System Configuration» anacron not working in ascii [SOLVED]
  1244. Pages:1Post reply
  1245. #12018-02-24 06:17:03
  1246. GNUser
  1247. Member
  1248.  
  1249. Registered: 2017-03-16
  1250. Posts: 535
  1251. Email
  1252. Anacron is not running on my laptop, regardless of whether it is plugged in or not.
  1253.  
  1254. Here is my /etc/anacrontab (it is the same as on my Devuan Jessie partition):
  1255.  
  1256. # /etc/anacrontab: configuration file for anacron
  1257.  
  1258. # See anacron(8) and anacrontab(5) for details.
  1259.  
  1260. SHELL=/bin/sh
  1261. PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
  1262. HOME=/root
  1263. LOGNAME=root
  1264.  
  1265. # These replace cron's entries
  1266. 1 5 cron.daily run-parts --report /etc/cron.daily
  1267. 7 10 cron.weekly run-parts --report /etc/cron.weekly
  1268. @monthly 15 cron.monthly run-parts --report /etc/cron.monthly
  1269.  
  1270. # bruno
  1271. 7 1 maintenance /opt/scripts/jobs-maintenance
  1272. Here is /etc/default/anacrontab:
  1273.  
  1274. # If set to "yes", start anacron even when on battery power. By
  1275. # default, the /etc/init.d/anacron script tries to avoid running
  1276. # anacron unless on AC power, so as to avoid running down the battery.
  1277. # (Things like the locate updatedb cause a lot of I/O.)
  1278.  
  1279. ANACRON_RUN_ON_BATTERY_POWER=yes
  1280. I already did this, too (I had to do it in Jessie in order for anacron to run while on battery power):
  1281.  
  1282. $ sudo chmod a-x /usr/lib/pm-utils/power.d/anacron
  1283. Looking at /var/log/syslog shows no entries by anacron. Also, /var/spool/anacron is an empty directory with no timestamps. I've tried rebooting and resuming from suspend, both on AC and battery power, and anacron gives no signs of life.
  1284.  
  1285. I have the 2.3-24 version installed. I also tried uninstalling it and installing the 2.3-23 version from Devuan Jessie and it made no difference.
  1286.  
  1287. Any ideas? Anacron is mission-critical for me.
  1288.  
  1289. Last edited by GNUser (2018-02-24 17:55:32)
  1290.  
  1291. Offline
  1292.  
  1293. Report Quote
  1294. #22018-02-24 06:40:03
  1295. GNUser
  1296. Member
  1297.  
  1298. Registered: 2017-03-16
  1299. Posts: 535
  1300. Email
  1301. After much snooping around, I discovered that /usr/sbin/anacron was a link to /bin/true (???)
  1302. The anacron package actually installs /usr/sbin/anacron.orig.anacron (???)
  1303. This fixed the issue: sudo ln -fs /usr/sbin/anacron.orig.anacron /usr/sbin/anacron
  1304.  
  1305. Very, very strange.
  1306.  
  1307. Offline
  1308.  
  1309. Report Quote
  1310. #32018-02-24 14:31:01
  1311. fsmithred
  1312. Administrator
  1313.  
  1314. Registered: 2016-11-25
  1315. Posts: 2,064
  1316. Email
  1317. I just checked one of my ascii installs, and /usr/sbin/anacron is a real file. There are entries in /var/log/syslog, and it looks like it runs when I boot the VM. My anacrontab looks like yours, there are files in /var/spool/anacron for cron.daily .weekly and .monthly with timestamps that match what syslog shows. And my /etc/default/anacron says "No".
  1318.  
  1319. 'apt-file find /usr/sbin/anacron.orig.anacron' turned up nothing. Maybe dpkg -S would show something on your end. Or 'grep anacron /root/.history' to see if you did something and forgot about it.
  1320.  
  1321. Offline
  1322.  
  1323. Report Quote
  1324. #42018-02-24 15:19:44
  1325. GNUser
  1326. Member
  1327.  
  1328. Registered: 2017-03-16
  1329. Posts: 535
  1330. Email
  1331. Thank you for the suggestions, fsmithred.
  1332.  
  1333. I have begun solving the mystery:
  1334.  
  1335. bruno@thinkpad:~$ dpkg -S anacron.orig.anacron
  1336. diversion by live-config from: /usr/sbin/anacron
  1337. diversion by live-config to: /usr/sbin/anacron.orig.anacron
  1338.  
  1339. bruno@thinkpad:~$ dpkg -l | grep live-config
  1340. ii live-config 5.20170112+deb9u1 all Live System Configuration Components
  1341. ii live-config-doc 5.20170112+deb9u1 all Live System Configuration Components (documentation)
  1342. ii live-config-sysvinit 5.20170112+deb9u1 all Live System Configuration Components (sysvinit backend)
  1343. I did not install any live-config packages, so they must have come with Miyo. I will try uninstalling live-config* and reinstalling anacron.
  1344.  
  1345. Offline
  1346.  
  1347. Report Quote
  1348. #52018-02-24 15:29:38
  1349. GNUser
  1350. Member
  1351.  
  1352. Registered: 2017-03-16
  1353. Posts: 535
  1354. Email
  1355. No luck. I purged all three live-config packages and ancron, rebooted, and reinstalled anacron. Similar shenanigans (at least now the symlink is pointing to something sensible and not /bin/true):
  1356.  
  1357. bruno@thinkpad:~$ ls -l /usr/sbin/anacron
  1358. lrwxrwxrwx 1 root root 30 Feb 24 01:36 /usr/sbin/anacron -> /usr/sbin/anacron.orig.anacron
  1359. bruno@thinkpad:~$ dpkg -S anacron.orig.anacron
  1360. diversion by live-config from: /usr/sbin/anacron
  1361. diversion by live-config to: /usr/sbin/anacron.orig.anacron
  1362. This is my /etc/apt/sources.list:
  1363.  
  1364. deb http://pkgmaster.devuan.org/merged/ ascii main
  1365. deb http://pkgmaster.devuan.org/merged/ ascii-security main
  1366. deb http://pkgmaster.devuan.org/merged/ ascii-updates main
  1367. fsmithred, are you sure that your /usr/sbin/anacron is a real file and not a link? If you are sure, what am I missing?
  1368.  
  1369. What is this live-config business anyway? Can I get rid of it?
  1370.  
  1371. Last edited by GNUser (2018-02-24 15:30:49)
  1372.  
  1373. Offline
  1374.  
  1375. Report Quote
  1376. #62018-02-24 17:54:40
  1377. GNUser
  1378. Member
  1379.  
  1380. Registered: 2017-03-16
  1381. Posts: 535
  1382. Email
  1383. I got it. Even after uninstalling the live-config* packages, the diversion that it created continues to live in dpkg, so one has to manually remove the diversion:
  1384.  
  1385. root@thinkpad:/home/bruno# dpkg-divert --list | grep anacron
  1386. diversion of /usr/sbin/anacron to /usr/sbin/anacron.orig.anacron by live-config
  1387.  
  1388. root@thinkpad:/home/bruno# dpkg-divert --remove /usr/sbin/anacron
  1389.  
  1390. root@thinkpad:/home/bruno# dpkg-divert --list | grep anacron
  1391. # no hits
  1392. Now I reinstall anacron and /usr/sbin/anacron is a real file as expected smile
  1393.  
  1394. Last edited by GNUser (2018-02-24 17:56:23)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!