API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Feb 21st, 2022
37
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 50.56 KB | None | 0 0
raw download clone embed print report
  1. -- The job identifier is 519.
  2. Feb 21 16:28:59 HomeServer rpc.statd[561]: Version 1.3.3 starting
  3. Feb 21 16:28:59 HomeServer rpc.statd[561]: Flags: TI-RPC
  4. Feb 21 16:28:59 HomeServer rpc.mountd[565]: Version 1.3.3 starting
  5. Feb 21 16:28:59 HomeServer systemd[1]: Started NFS Mount Daemon.
  6. -- Subject: A start job for unit nfs-mountd.service has finished successfully
  7. -- Defined-By: systemd
  8. -- Support: https://www.debian.org/support
  9. --
  10. -- A start job for unit nfs-mountd.service has finished successfully.
  11. --
  12. -- The job identifier is 106.
  13. Feb 21 16:28:59 HomeServer systemd[1]: Started NFS status monitor for NFSv2/3 locking..
  14. -- Subject: A start job for unit rpc-statd.service has finished successfully
  15. -- Defined-By: systemd
  16. -- Support: https://www.debian.org/support
  17. --
  18. -- A start job for unit rpc-statd.service has finished successfully.
  19. --
  20. -- The job identifier is 107.
  21. Feb 21 16:28:59 HomeServer systemd[1]: Starting NFS server and services...
  22. -- Subject: A start job for unit nfs-server.service has begun execution
  23. -- Defined-By: systemd
  24. -- Support: https://www.debian.org/support
  25. --
  26. -- A start job for unit nfs-server.service has begun execution.
  27. --
  28. -- The job identifier is 103.
  29. Feb 21 16:29:00 HomeServer avahi-daemon[462]: Server startup complete. Host name is HomeServer.local. Local service cookie is 128000546.
  30. Feb 21 16:29:01 HomeServer avahi-daemon[462]: Service "HomeServer - Web control panel" (/services/website.service) successfully established.
  31. Feb 21 16:29:01 HomeServer avahi-daemon[462]: Service "HomeServer - SSH" (/services/ssh.service) successfully established.
  32. Feb 21 16:29:01 HomeServer avahi-daemon[462]: Service "HomeServer - SMB/CIFS" (/services/smb.service) successfully established.
  33. -- The job identifier is 103.
  34. Feb 21 16:29:00 HomeServer avahi-daemon[462]: Server startup complete. Host name is HomeServer.local. Local service cookie is 128000546.
  35. Feb 21 16:29:01 HomeServer avahi-daemon[462]: Service "HomeServer - Web control panel" (/services/website.service) successfully established.
  36. Feb 21 16:29:01 HomeServer avahi-daemon[462]: Service "HomeServer - SSH" (/services/ssh.service) successfully established.
  37. Feb 21 16:29:01 HomeServer avahi-daemon[462]: Service "HomeServer - SMB/CIFS" (/services/smb.service) successfully established.
  38. Feb 21 16:29:01 HomeServer sshd[616]: Server listening on 0.0.0.0 port 22.
  39. Feb 21 16:29:01 HomeServer sshd[616]: Server listening on :: port 22.
  40. Feb 21 16:29:01 HomeServer systemd[1]: Started OpenBSD Secure Shell server.
  41. -- Subject: A start job for unit ssh.service has finished successfully
  42. -- Defined-By: systemd
  43. -- Support: https://www.debian.org/support
  44. --
  45. -- A start job for unit ssh.service has finished successfully.
  46. --
  47. -- The job identifier is 102.
  48. Feb 21 16:29:01 HomeServer nfsdcltrack[615]: Storage directory /var/lib/nfs/nfsdcltrack is not writable. Should be owned by root and writable by owner!
  49. Feb 21 16:29:02 HomeServer nfsdcltrack[615]: Failed to init database: 14
  50. Feb 21 16:29:02 HomeServer kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
  51. Feb 21 16:29:02 HomeServer kernel: NFSD: Using legacy client tracking operations.
  52. Feb 21 16:29:02 HomeServer kernel: NFSD: starting 90-second grace period (net f0000098)
  53. Feb 21 16:29:02 HomeServer systemd[1]: Started NFS server and services.
  54. -- Subject: A start job for unit nfs-server.service has finished successfully
  55. -- Defined-By: systemd
  56. -- Support: https://www.debian.org/support
  57. --
  58. -- A start job for unit nfs-server.service has finished successfully.
  59. --
  60. -- The job identifier is 103.
  61. Feb 21 16:29:02 HomeServer systemd[1]: Starting Notify NFS peers of a restart...
  62. -- Subject: A start job for unit rpc-statd-notify.service has begun execution
  63. -- Defined-By: systemd
  64. -- Support: https://www.debian.org/support
  65. --
  66. -- A start job for unit rpc-statd-notify.service has begun execution.
  67. --
  68. -- The job identifier is 109.
  69. Feb 21 16:29:02 HomeServer systemd[1]: Reached target Remote File Systems (Pre).
  70. -- Subject: A start job for unit remote-fs-pre.target has finished successfully
  71. -- Defined-By: systemd
  72. -- Support: https://www.debian.org/support
  73. --
  74. -- A start job for unit remote-fs-pre.target has finished successfully.
  75. --
  76. -- The job identifier is 85.
  77. Feb 21 16:29:02 HomeServer systemd[1]: Reached target Remote File Systems.
  78. -- Subject: A start job for unit remote-fs.target has finished successfully
  79. -- Defined-By: systemd
  80. -- Support: https://www.debian.org/support
  81. --
  82. -- A start job for unit remote-fs.target has finished successfully.
  83. --
  84. -- The job identifier is 83.
  85. Feb 21 16:29:02 HomeServer systemd[1]: Starting LSB: Load kernel modules needed to enable cpufreq scaling...
  86. -- Subject: A start job for unit loadcpufreq.service has begun execution
  87. -- Defined-By: systemd
  88. -- Support: https://www.debian.org/support
  89. --
  90. -- A start job for unit loadcpufreq.service has begun execution.
  91. --
  92. -- The job identifier is 131.
  93. Feb 21 16:29:02 HomeServer systemd[1]: Starting LSB: service and resource monitoring daemon...
  94. -- Subject: A start job for unit monit.service has begun execution
  95. -- Defined-By: systemd
  96. -- Support: https://www.debian.org/support
  97. -- The job identifier is 130.
  98. Feb 21 16:29:02 HomeServer systemd[1]: Starting LSB: start or stop rrdcached...
  99. -- Subject: A start job for unit rrdcached.service has begun execution
  100. -- Defined-By: systemd
  101. -- Support: https://www.debian.org/support
  102. --
  103. -- A start job for unit rrdcached.service has begun execution.
  104. --
  105. -- The job identifier is 115.
  106. Feb 21 16:29:02 HomeServer systemd[1]: Started Regular background program processing daemon.
  107. -- Subject: A start job for unit cron.service has finished successfully
  108. -- Defined-By: systemd
  109. -- Support: https://www.debian.org/support
  110. --
  111. -- A start job for unit cron.service has finished successfully.
  112. --
  113. -- The job identifier is 123.
  114. Feb 21 16:29:02 HomeServer systemd[1]: Starting Permit User Sessions...
  115. -- Subject: A start job for unit systemd-user-sessions.service has begun execution
  116. -- Defined-By: systemd
  117. -- Support: https://www.debian.org/support
  118. --
  119. -- A start job for unit systemd-user-sessions.service has begun execution.
  120. --
  121. -- The job identifier is 93.
  122. Feb 21 16:29:02 HomeServer sm-notify[625]: Version 1.3.3 starting
  123. Feb 21 16:29:02 HomeServer systemd[1]: Started Permit User Sessions.
  124. -- Subject: A start job for unit systemd-user-sessions.service has finished successfully
  125. -- Defined-By: systemd
  126. -- Support: https://www.debian.org/support
  127. --
  128. -- A start job for unit systemd-user-sessions.service has finished successfully.
  129. --
  130. -- The job identifier is 93.
  131. Feb 21 16:29:02 HomeServer systemd[1]: Started Getty on tty1.
  132. -- Subject: A start job for unit getty@tty1.service has finished successfully
  133. -- Defined-By: systemd
  134. -- Support: https://www.debian.org/support
  135. --
  136. -- A start job for unit getty@tty1.service has finished successfully.
  137. --
  138. -- The job identifier is 143.
  139. Feb 21 16:29:02 HomeServer cron[629]: (CRON) INFO (pidfile fd = 3)
  140. Feb 21 16:29:02 HomeServer systemd[1]: rpc-statd-notify.service: Succeeded.
  141. -- Subject: Unit succeeded
  142. -- Defined-By: systemd
  143. -- Support: https://www.debian.org/support
  144. --
  145. -- The unit rpc-statd-notify.service has successfully entered the 'dead' state.
  146. Feb 21 16:29:02 HomeServer systemd[1]: Started Notify NFS peers of a restart.
  147. -- Subject: A start job for unit rpc-statd-notify.service has finished successfully
  148. -- Defined-By: systemd
  149. -- Support: https://www.debian.org/support
  150. --
  151. -- A start job for unit rpc-statd-notify.service has finished successfully.
  152. --
  153. -- The job identifier is 109.
  154. Feb 21 16:29:03 HomeServer cron[629]: (CRON) INFO (Running @reboot jobs)
  155. Feb 21 16:29:03 HomeServer loadcpufreq[626]: Loading cpufreq kernel modules...done (acpi-cpufreq).
  156. Feb 21 16:29:04 HomeServer systemd[1]: Started LSB: Load kernel modules needed to enable cpufreq scaling.
  157. -- Subject: A start job for unit loadcpufreq.service has finished successfully
  158. -- Defined-By: systemd
  159. -- Support: https://www.debian.org/support
  160. --
  161. -- A start job for unit loadcpufreq.service has finished successfully.
  162. --
  163. -- A start job for unit loadcpufreq.service has finished successfully.
  164. --
  165. -- The job identifier is 131.
  166. Feb 21 16:29:04 HomeServer systemd[1]: Starting LSB: set CPUFreq kernel parameters...
  167. -- Subject: A start job for unit cpufrequtils.service has begun execution
  168. -- Defined-By: systemd
  169. -- Support: https://www.debian.org/support
  170. --
  171. -- A start job for unit cpufrequtils.service has begun execution.
  172. --
  173. -- The job identifier is 96.
  174. Feb 21 16:29:04 HomeServer cpufrequtils[697]: CPUFreq Utilities: Setting conservative CPUFreq governor...CPU0...CPU1...CPU2...CPU3...done.
  175. Feb 21 16:29:04 HomeServer systemd[1]: Started LSB: set CPUFreq kernel parameters.
  176. -- Subject: A start job for unit cpufrequtils.service has finished successfully
  177. -- Defined-By: systemd
  178. -- Support: https://www.debian.org/support
  179. --
  180. -- A start job for unit cpufrequtils.service has finished successfully.
  181. --
  182. -- The job identifier is 96.
  183. Feb 21 16:29:05 HomeServer monit[645]: Starting Monit 5.26.0 daemon with http interface at /run/monit.sock
  184. Feb 21 16:29:05 HomeServer monit[627]: Starting daemon monitor: monit.
  185. Feb 21 16:29:05 HomeServer systemd[1]: Started LSB: service and resource monitoring daemon.
  186. -- Subject: A start job for unit monit.service has finished successfully
  187. -- Defined-By: systemd
  188. -- Support: https://www.debian.org/support
  189. --
  190. -- A start job for unit monit.service has finished successfully.
  191. --
  192. -- The job identifier is 130.
  193. Feb 21 16:29:05 HomeServer monit[720]: Monit will delay for 5s on first start after reboot ...
  194. Feb 21 16:29:05 HomeServer postfix/postfix-script[739]: warning: symlink leaves directory: /etc/postfix/./makedefs.out
  195. Feb 21 16:29:05 HomeServer postfix/postfix-script[743]: warning: not owned by postfix: /var/lib/postfix/.
  196. Feb 21 16:29:05 HomeServer postfix/postfix-script[746]: warning: not owned by postfix: /var/lib/postfix/./prng_exch
  197. Feb 21 16:29:05 HomeServer postfix/postfix-script[747]: warning: not owned by postfix: /var/lib/postfix/./master.lock
  198. Feb 21 16:29:06 HomeServer postfix/postfix-script[768]: starting the Postfix mail system
  199. Feb 21 16:29:06 HomeServer postfix/master[770]: fatal: open lock file /var/lib/postfix/master.lock: cannot open file: Permission denied
  200. Feb 21 16:29:06 HomeServer rrdcached[628]: rrdcached started.
  201. Feb 21 16:29:06 HomeServer systemd[1]: Started LSB: start or stop rrdcached.
  202. -- Subject: A start job for unit rrdcached.service has finished successfully
  203. -- Defined-By: systemd
  204. -- Support: https://www.debian.org/support
  205. --
  206. -- A start job for unit rrdcached.service has finished successfully.
  207. --
  208. -- The job identifier is 115.
  209. Feb 21 16:29:06 HomeServer systemd[1]: Starting Statistics collection and monitoring daemon...
  210. -- Subject: A start job for unit collectd.service has begun execution
  211. -- Defined-By: systemd
  212. -- Support: https://www.debian.org/support
  213. --
  214. -- A start job for unit collectd.service has begun execution.
  215. --
  216. -- The job identifier is 114.
  217. Feb 21 16:29:07 HomeServer postfix/master[769]: fatal: daemon initialization failure
  218. Feb 21 16:29:08 HomeServer postfix/postfix-script[781]: fatal: mail system startup failed
  219. Feb 21 16:29:08 HomeServer collectd[780]: plugin_load: plugin "cpu" successfully loaded.
  220. Feb 21 16:29:08 HomeServer collectd[780]: plugin_load: plugin "df" successfully loaded.
  221. Feb 21 16:29:08 HomeServer systemd[1]: Started A high performance web server and a reverse proxy server.
  222. -- Subject: A start job for unit nginx.service has finished successfully
  223. -- Defined-By: systemd
  224. -- Support: https://www.debian.org/support
  225. --
  226. -- A start job for unit nginx.service has finished successfully.
  227. --
  228. -- The job identifier is 128.
  229. Feb 21 16:29:08 HomeServer collectd[780]: plugin_load: plugin "disk" successfully loaded.
  230. Feb 21 16:29:08 HomeServer collectd[780]: plugin_load: plugin "interface" successfully loaded.
  231. Feb 21 16:29:08 HomeServer collectd[780]: plugin_load: plugin "load" successfully loaded.
  232. Feb 21 16:29:09 HomeServer collectd[780]: plugin_load: plugin "memory" successfully loaded.
  233. Feb 21 16:29:09 HomeServer systemd[1]: Started The PHP 7.3 FastCGI Process Manager.
  234. -- Subject: A start job for unit php7.3-fpm.service has finished successfully
  235. -- Defined-By: systemd
  236. -- Support: https://www.debian.org/support
  237. --
  238. -- A start job for unit php7.3-fpm.service has finished successfully.
  239. --
  240. -- The job identifier is 99.
  241. Feb 21 16:29:09 HomeServer systemd[1]: phpsessionclean.service: Succeeded.
  242. -- Subject: Unit succeeded
  243. -- Defined-By: systemd
  244. -- Support: https://www.debian.org/support
  245. --
  246. -- The unit phpsessionclean.service has successfully entered the 'dead' state.
  247. Feb 21 16:29:09 HomeServer systemd[1]: Started Clean php session files.
  248. -- Subject: A start job for unit phpsessionclean.service has finished successfully
  249. -- Defined-By: systemd
  250. -- Support: https://www.debian.org/support
  251. --
  252. -- A start job for unit phpsessionclean.service has finished successfully.
  253. --
  254. -- The job identifier is 432.
  255. Feb 21 16:29:09 HomeServer systemd[1]: postfix@-.service: Control process exited, code=exited, status=1/FAILURE
  256. -- Subject: Unit process exited
  257. -- Defined-By: systemd
  258. -- Support: https://www.debian.org/support
  259. --
  260. -- An ExecStart= process belonging to unit postfix@-.service has exited.
  261. --
  262. -- The process' exit code is 'exited' and its exit status is 1.
  263. Feb 21 16:29:09 HomeServer systemd[1]: postfix@-.service: Failed with result 'exit-code'.
  264. --
  265. -- The unit postfix@-.service has entered the 'failed' state with result 'exit-code'.
  266. Feb 21 16:29:09 HomeServer systemd[1]: Failed to start Postfix Mail Transport Agent (instance -).
  267. -- Subject: A start job for unit postfix@-.service has failed
  268. -- Defined-By: systemd
  269. -- Support: https://www.debian.org/support
  270. --
  271. -- A start job for unit postfix@-.service has finished with a failure.
  272. --
  273. -- The job identifier is 137 and the job result is failed.
  274. Feb 21 16:29:09 HomeServer systemd[1]: Starting Postfix Mail Transport Agent...
  275. -- Subject: A start job for unit postfix.service has begun execution
  276. -- Defined-By: systemd
  277. -- Support: https://www.debian.org/support
  278. --
  279. -- A start job for unit postfix.service has begun execution.
  280. --
  281. -- The job identifier is 136.
  282. Feb 21 16:29:09 HomeServer systemd[1]: Started Postfix Mail Transport Agent.
  283. -- Subject: A start job for unit postfix.service has finished successfully
  284. -- Defined-By: systemd
  285. -- Support: https://www.debian.org/support
  286. --
  287. -- A start job for unit postfix.service has finished successfully.
  288. --
  289. -- The job identifier is 136.
  290. Feb 21 16:29:09 HomeServer systemd[1]: openmediavault-engined.service: Supervising process 837 which is not our child. We'll most likely not notice when
  291. Feb 21 16:29:09 HomeServer systemd[1]: Started The OpenMediaVault engine daemon that processes the RPC request.
  292. -- Subject: A start job for unit openmediavault-engined.service has finished successfully
  293. -- Defined-By: systemd
  294. -- Support: https://www.debian.org/support
  295. --
  296. -- A start job for unit openmediavault-engined.service has finished successfully.
  297. --
  298. -- The job identifier is 121.
  299. Feb 21 16:29:09 HomeServer collectd[780]: plugin_load: plugin "rrdcached" successfully loaded.
  300. Feb 21 16:29:09 HomeServer collectd[780]: plugin_load: plugin "syslog" successfully loaded.
  301. Feb 21 16:29:09 HomeServer collectd[780]: plugin_load: plugin "unixsock" successfully loaded.
  302. Feb 21 16:29:09 HomeServer collectd[780]: plugin_load: plugin "uptime" successfully loaded.
  303. Feb 21 16:29:09 HomeServer collectd[780]: Systemd detected, trying to signal readyness.
  304. Feb 21 16:29:09 HomeServer systemd[1]: Started Statistics collection and monitoring daemon.
  305. -- Subject: A start job for unit collectd.service has finished successfully
  306. -- Defined-By: systemd
  307. -- Support: https://www.debian.org/support
  308. --
  309. -- A start job for unit collectd.service has finished successfully.
  310. --
  311. -- The job identifier is 114.
  312. Feb 21 16:29:09 HomeServer collectd[780]: Initialization complete, entering read-loop.
  313. Feb 21 16:29:10 HomeServer monit[720]: 'HomeServer' Monit 5.26.0 started
  314. Feb 21 16:29:10 HomeServer monit[720]: Aborting queued event '/var/lib/monit/events/1645358210_556cd0832640' - service filesystem_srv_dev-disk-by-uuid-8
  315. Feb 21 16:29:10 HomeServer monit[720]: Aborting queued event '/var/lib/monit/events/1645358240_556cd08253b0' - service mountpoint_srv_dev-disk-by-uuid-8
  316. Feb 21 16:29:12 HomeServer wsdd.py[551]: WARNING: no interface given, using all interfaces
  317. Feb 21 16:29:13 HomeServer fail2ban-server[555]: Server ready
  318. Feb 21 16:29:14 HomeServer systemd[1]: apt-daily.service: Succeeded.
  319. -- Subject: Unit succeeded
  320. -- Defined-By: systemd
  321. -- Support: https://www.debian.org/support
  322. --
  323. -- The unit apt-daily.service has successfully entered the 'dead' state.
  324. Feb 21 16:29:14 HomeServer systemd[1]: Started Daily apt download activities.
  325. -- Subject: A start job for unit apt-daily.service has finished successfully
  326. -- Defined-By: systemd
  327. -- Support: https://www.debian.org/support
  328. --
  329. -- A start job for unit apt-daily.service has finished successfully.
  330. --
  331. -- The job identifier is 171.
  332. Feb 21 16:29:14 HomeServer systemd[1]: Starting Daily apt upgrade and clean activities...
  333. -- Subject: A start job for unit apt-daily-upgrade.service has begun execution
  334. -- Defined-By: systemd
  335. -- Support: https://www.debian.org/support
  336. --
  337. -- A start job for unit apt-daily-upgrade.service has begun execution.
  338. --
  339. -- The job identifier is 258.
  340. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.085034960+01:00" level=info msg="starting containerd" revision=7b11cfaabd73bb80907
  341. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.171638960+01:00" level=info msg="loading plugin \"io.containerd.content.v1.content
  342. Feb 21 16:29:15 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
  343. -- Subject: Unit process exited
  344. -- Defined-By: systemd
  345. -- Support: https://www.debian.org/support
  346. --
  347. -- An ExecStart= process belonging to unit smbd.service has exited.
  348. --
  349. -- The process' exit code is 'exited' and its exit status is 1.
  350. Feb 21 16:29:15 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
  351. -- Subject: Unit failed
  352. -- Defined-By: systemd
  353. -- Support: https://www.debian.org/support
  354. --
  355. -- The unit smbd.service has entered the 'failed' state with result 'exit-code'.
  356. Feb 21 16:29:15 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
  357. -- Subject: A start job for unit smbd.service has failed
  358. -- Defined-By: systemd
  359. -- Support: https://www.debian.org/support
  360. --
  361. -- A start job for unit smbd.service has finished with a failure.
  362. --
  363. -- The job identifier is 125 and the job result is failed.
  364. Feb 21 16:29:15 HomeServer systemd[1]: Stopping Web Services Dynamic Discovery host daemon...
  365. -- Subject: A stop job for unit wsdd.service has begun execution
  366. -- Defined-By: systemd
  367. -- Support: https://www.debian.org/support
  368. --
  369. -- A stop job for unit wsdd.service has begun execution.
  370. --
  371. -- The job identifier is 607.
  372. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.239268080+01:00" level=info msg="loading plugin \"io.containerd.snapshotter.v1.aufs\"..." type=io.containerd.snapshotter.v1
  373. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.242199600+01:00" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.aufs\"..." error="aufs is not supported (modprobe aufs failed: exit status 1 \
  374. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.242262600+01:00" level=info msg="loading plugin \"io.containerd.snapshotter.v1.btrfs\"..." type=io.containerd.snapshotter.v1
  375. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.242832160+01:00" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.btrfs\"..." error="path /var/lib/containerd/io.containerd.snapshotter.v1.btrfs
  376. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.242880440+01:00" level=info msg="loading plugin \"io.containerd.snapshotter.v1.devmapper\"..." type=io.containerd.snapshotter.v1
  377. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.242934080+01:00" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured"
  378. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.242966600+01:00" level=info msg="loading plugin \"io.containerd.snapshotter.v1.native\"..." type=io.containerd.snapshotter.v1
  379. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.257778600+01:00" level=info msg="loading plugin \"io.containerd.snapshotter.v1.overlayfs\"..." type=io.containerd.snapshotter.v1
  380. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.265604160+01:00" level=info msg="loading plugin \"io.containerd.snapshotter.v1.zfs\"..." type=io.containerd.snapshotter.v1
  381. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.266154840+01:00" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.zfs\"..." error="path /var/lib/containerd/io.containerd.snapshotter.v1.zfs mus
  382. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.266218640+01:00" level=info msg="loading plugin \"io.containerd.metadata.v1.bolt\"..." type=io.containerd.metadata.v1
  383. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.266276560+01:00" level=warning msg="could not use snapshotter devmapper in metadata plugin" error="devmapper not configured"
  384. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.266308480+01:00" level=info msg="metadata content store policy set" policy=shared
  385. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.335986320+01:00" level=info msg="loading plugin \"io.containerd.differ.v1.walking\"..." type=io.containerd.differ.v1
  386. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.336734760+01:00" level=info msg="loading plugin \"io.containerd.gc.v1.scheduler\"..." type=io.containerd.gc.v1
  387. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.336965160+01:00" level=info msg="loading plugin \"io.containerd.service.v1.introspection-service\"..." type=io.containerd.service.v1
  388. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337050040+01:00" level=info msg="loading plugin \"io.containerd.service.v1.containers-service\"..." type=io.containerd.service.v1
  389. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337080040+01:00" level=info msg="loading plugin \"io.containerd.service.v1.content-service\"..." type=io.containerd.service.v1
  390. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337114280+01:00" level=info msg="loading plugin \"io.containerd.service.v1.diff-service\"..." type=io.containerd.service.v1
  391. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337150280+01:00" level=info msg="loading plugin \"io.containerd.service.v1.images-service\"..." type=io.containerd.service.v1
  392. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337194000+01:00" level=info msg="loading plugin \"io.containerd.service.v1.leases-service\"..." type=io.containerd.service.v1
  393. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337225280+01:00" level=info msg="loading plugin \"io.containerd.service.v1.namespaces-service\"..." type=io.containerd.service.v1
  394. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337252920+01:00" level=info msg="loading plugin \"io.containerd.service.v1.snapshots-service\"..." type=io.containerd.service.v1
  395. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337290640+01:00" level=info msg="loading plugin \"io.containerd.runtime.v1.linux\"..." type=io.containerd.runtime.v1
  396. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337480880+01:00" level=info msg="loading plugin \"io.containerd.runtime.v2.task\"..." type=io.containerd.runtime.v2
  397. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.337589160+01:00" level=info msg="loading plugin \"io.containerd.monitor.v1.cgroups\"..." type=io.containerd.monitor.v1
  398. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338405640+01:00" level=info msg="loading plugin \"io.containerd.service.v1.tasks-service\"..." type=io.containerd.service.v1
  399. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338495120+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.restart\"..." type=io.containerd.internal.v1
  400. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338595400+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.containers\"..." type=io.containerd.grpc.v1
  401. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338636000+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.content\"..." type=io.containerd.grpc.v1
  402. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338672440+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.diff\"..." type=io.containerd.grpc.v1
  403. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338707560+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.events\"..." type=io.containerd.grpc.v1
  404. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338742960+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.healthcheck\"..." type=io.containerd.grpc.v1
  405. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338788760+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.images\"..." type=io.containerd.grpc.v1
  406. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338825000+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.leases\"..." type=io.containerd.grpc.v1
  407. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338872240+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.namespaces\"..." type=io.containerd.grpc.v1
  408. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.338908240+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.opt\"..." type=io.containerd.internal.v1
  409. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.446350400+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.snapshots\"..." type=io.containerd.grpc.v1
  410. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.446493560+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.tasks\"..." type=io.containerd.grpc.v1
  411. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.446536440+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.version\"..." type=io.containerd.grpc.v1
  412. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.446579000+01:00" level=info msg="loading plugin \"io.containerd.grpc.v1.introspection\"..." type=io.containerd.grpc.v1
  413. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.461417000+01:00" level=info msg=serving... address=/run/containerd/containerd.sock.ttrpc
  414. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.461602320+01:00" level=info msg=serving... address=/run/containerd/containerd.sock
  415. Feb 21 16:29:15 HomeServer containerd[559]: time="2022-02-21T16:29:15.461748240+01:00" level=info msg="containerd successfully booted in 0.540626s"
  416.  
  417. -- The job identifier is 147.
  418. Feb 21 16:30:11 HomeServer systemd[1]: Reloading.
  419. Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
  420. Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
  421. Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/rpc-statd.service:13: PIDFile= references path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingl
  422. Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit
  423. Feb 21 16:30:11 HomeServer systemd[1]: getty@tty1.service: Current command vanished from the unit file, execution of the command list won't be resumed.
  424. Feb 21 16:30:11 HomeServer systemd[1]: avahi-daemon.service: Current command vanished from the unit file, execution of the command list won't be resumed.
  425. Feb 21 16:30:11 HomeServer systemd[1]: run-r2cdd605284754357b350c5531ecef872.scope: Succeeded.
  426. -- Subject: Unit succeeded
  427. -- Defined-By: systemd
  428. -- Support: https://www.debian.org/support
  429.  
  430. -- The unit run-r2cdd605284754357b350c5531ecef872.scope has successfully entered the 'dead' state.
  431. Feb 21 16:30:11 HomeServer systemd[1]: Reached target Login Prompts.
  432. -- Subject: A start job for unit getty.target has finished successfully
  433. -- Defined-By: systemd
  434. -- Support: https://www.debian.org/support
  435. --
  436. -- A start job for unit getty.target has finished successfully.
  437. --
  438. -- The job identifier is 142.
  439. Feb 21 16:30:11 HomeServer systemd[1]: Reached target Multi-User System.
  440. -- Subject: A start job for unit multi-user.target has finished successfully
  441. -- Defined-By: systemd
  442. -- Support: https://www.debian.org/support
  443. --
  444. -- A start job for unit multi-user.target has finished successfully.
  445. --
  446. -- The job identifier is 2.
  447. Feb 21 16:30:11 HomeServer systemd[1]: Reached target Graphical Interface.
  448. -- Subject: A start job for unit graphical.target has finished successfully
  449. -- Defined-By: systemd
  450. -- Support: https://www.debian.org/support
  451. --
  452. -- A start job for unit graphical.target has finished successfully.
  453. --
  454. -- The job identifier is 1.
  455. Feb 21 16:30:11 HomeServer systemd[1]: Starting watchdog daemon...
  456. -- Subject: A start job for unit watchdog.service has begun execution
  457. -- Defined-By: systemd
  458. -- Support: https://www.debian.org/support
  459. --
  460. -- A start job for unit watchdog.service has begun execution.
  461. --
  462. -- The job identifier is 151.
  463. Feb 21 16:30:11 HomeServer systemd[1]: Starting Beep after system start...
  464. -- Subject: A start job for unit openmediavault-beep-up.service has begun execution
  465. -- Defined-By: systemd
  466. -- Support: https://www.debian.org/support
  467. --
  468. -- A start job for unit openmediavault-beep-up.service has begun execution.
  469. --
  470. -- The job identifier is 82.
  471. Feb 21 16:30:11 HomeServer systemd[1]: Starting Update UTMP about System Runlevel Changes...
  472. -- Subject: A start job for unit systemd-update-utmp-runlevel.service has begun execution
  473. -- Defined-By: systemd
  474. -- Support: https://www.debian.org/support
  475. --
  476. -- A start job for unit systemd-update-utmp-runlevel.service has begun execution.
  477. --
  478. -- The job identifier is 119.
  479. Feb 21 16:30:11 HomeServer systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
  480. -- Subject: Unit succeeded
  481. -- Defined-By: systemd
  482. -- Support: https://www.debian.org/support
  483. --
  484. -- The unit systemd-update-utmp-runlevel.service has successfully entered the 'dead' state.
  485. Feb 21 16:30:11 HomeServer systemd[1]: Started Update UTMP about System Runlevel Changes.
  486. -- Subject: A start job for unit systemd-update-utmp-runlevel.service has finished successfully
  487. -- Defined-By: systemd
  488. -- Support: https://www.debian.org/support
  489. --
  490. -- A start job for unit systemd-update-utmp-runlevel.service has finished successfully.
  491. --
  492. -- The job identifier is 119.
  493. Feb 21 16:30:11 HomeServer systemd[1]: Started /bin/systemctl stop avahi-daemon.socket.
  494. -- Subject: A start job for unit run-r161b1cb7961141b49d0e529bfe40e9f1.scope has finished successfully
  495. -- Defined-By: systemd
  496. -- Support: https://www.debian.org/support
  497. --
  498. -- A start job for unit run-r161b1cb7961141b49d0e529bfe40e9f1.scope has finished successfully.
  499. --
  500. -- The job identifier is 613.
  501. Feb 21 16:30:11 HomeServer systemd[1]: avahi-daemon.socket: Succeeded.
  502. -- Subject: Unit succeeded
  503. -- Defined-By: systemd
  504. -- Support: https://www.debian.org/support
  505. --
  506. -- The unit avahi-daemon.socket has successfully entered the 'dead' state.
  507. Feb 21 16:30:11 HomeServer systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
  508. -- Subject: A stop job for unit avahi-daemon.socket has finished
  509. -- Defined-By: systemd
  510. -- Support: https://www.debian.org/support
  511. --
  512. -- A stop job for unit avahi-daemon.socket has finished.
  513. --
  514. -- The job identifier is 617 and the job result is done.
  515. Feb 21 16:30:11 HomeServer systemd[1]: run-r161b1cb7961141b49d0e529bfe40e9f1.scope: Succeeded.
  516. -- Subject: Unit succeeded
  517. -- Defined-By: systemd
  518. -- Support: https://www.debian.org/support
  519. --
  520. -- The unit run-r161b1cb7961141b49d0e529bfe40e9f1.scope has successfully entered the 'dead' state.
  521. Feb 21 16:30:11 HomeServer systemd[1]: Started /bin/systemctl disable avahi-daemon.socket.
  522. -- Subject: A start job for unit run-r97fb0d9356e1498484bbf634f6280b7a.scope has finished successfully
  523. -- Defined-By: systemd
  524. -- Support: https://www.debian.org/support
  525. --
  526. -- A start job for unit run-r97fb0d9356e1498484bbf634f6280b7a.scope has finished successfully.
  527. --
  528. -- The job identifier is 618.
  529. Feb 21 16:30:11 HomeServer kernel: watchdog: Software Watchdog: cannot register miscdev on minor=130 (err=-16).
  530. Feb 21 16:30:11 HomeServer kernel: watchdog: Software Watchdog: a legacy watchdog module is probably present.
  531. Feb 21 16:30:11 HomeServer kernel: softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
  532. Feb 21 16:30:11 HomeServer kernel: softdog: soft_reboot_cmd=<not set> soft_active_on_boot=0
  533. Feb 21 16:30:11 HomeServer systemd[1]: Reloading.
  534. Feb 21 16:30:11 HomeServer watchdog[2279]: starting daemon (5.15):
  535. Feb 21 16:30:11 HomeServer watchdog[2279]: int=1s realtime=yes sync=no load=0,0,0 soft=no
  536. Feb 21 16:30:11 HomeServer watchdog[2279]: memory not checked
  537. Feb 21 16:30:11 HomeServer watchdog[2279]: ping: no machine to check
  538. Feb 21 16:30:11 HomeServer watchdog[2279]: file: no file to check
  539. Feb 21 16:30:11 HomeServer watchdog[2279]: pidfile: no server process to check
  540. Feb 21 16:30:11 HomeServer watchdog[2279]: interface: no interface to check
  541. Feb 21 16:30:11 HomeServer watchdog[2279]: temperature: no sensors to check
  542. Feb 21 16:30:11 HomeServer watchdog[2279]: no test binary files
  543. Feb 21 16:30:11 HomeServer watchdog[2279]: no repair binary files
  544. Feb 21 16:30:11 HomeServer watchdog[2279]: error retry time-out = 60 seconds
  545. Feb 21 16:30:11 HomeServer watchdog[2279]: repair attempts = 1
  546. Feb 21 16:30:11 HomeServer watchdog[2279]: alive=/dev/watchdog heartbeat=[none] to=root no_act=no force=no
  547. Feb 21 16:30:11 HomeServer watchdog[2279]: cannot set timeout 60 (errno = 22 = 'Invalid argument')
  548. Feb 21 16:30:11 HomeServer watchdog[2279]: hardware watchdog identity: NV_TCO
  549. Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
  550. Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
  551. Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/rpc-statd.service:13: PIDFile= references path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingl
  552. Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit
  553. Feb 21 16:30:12 HomeServer systemd[1]: watchdog.service: Current command vanished from the unit file, execution of the command list won't be resumed.
  554. Feb 21 16:30:12 HomeServer systemd[1]: Started watchdog daemon.
  555. -- Subject: A start job for unit watchdog.service has finished successfully
  556. -- Defined-By: systemd
  557. -- Support: https://www.debian.org/support
  558. --
  559. -- A start job for unit watchdog.service has finished successfully.
  560. --
  561. -- The job identifier is 151.
  562. Feb 21 16:30:12 HomeServer systemd[1]: run-r97fb0d9356e1498484bbf634f6280b7a.scope: Succeeded.
  563. -- Subject: Unit succeeded
  564. -- Defined-By: systemd
  565. -- Support: https://www.debian.org/support
  566. --
  567. -- The unit run-r97fb0d9356e1498484bbf634f6280b7a.scope has successfully entered the 'dead' state.
  568. Feb 21 16:30:12 HomeServer systemd[1]: openmediavault-beep-up.service: Succeeded.
  569. -- Subject: Unit succeeded
  570. -- Defined-By: systemd
  571. -- Support: https://www.debian.org/support
  572. --
  573. -- The unit openmediavault-beep-up.service has successfully entered the 'dead' state.
  574. Feb 21 16:30:12 HomeServer systemd[1]: Started Beep after system start.
  575. -- Subject: A start job for unit openmediavault-beep-up.service has finished successfully
  576. -- Defined-By: systemd
  577.  
  578. -- The job identifier is 628.
  579. Feb 21 16:30:13 HomeServer systemd[1]: Reloading.
  580. Feb 21 16:30:13 HomeServer systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
  581. Feb 21 16:30:13 HomeServer systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
  582. Feb 21 16:30:13 HomeServer systemd[1]: /lib/systemd/system/rpc-statd.service:13: PIDFile= references path below legacy directory /var/run/, updating /var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file accordingl
  583. Feb 21 16:30:13 HomeServer systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit
  584. Feb 21 16:30:13 HomeServer systemd[1]: run-rf9de7e8f45ee4a028fd51ef5207a6429.scope: Succeeded.
  585. -- Subject: Unit succeeded
  586. -- Defined-By: systemd
  587. -- Support: https://www.debian.org/support
  588.  
  589. -- The job identifier is 826.
  590. Feb 21 16:30:58 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
  591. -- Subject: Unit process exited
  592. -- Defined-By: systemd
  593. -- Support: https://www.debian.org/support
  594. --
  595. -- An ExecStart= process belonging to unit smbd.service has exited.
  596. --
  597. -- The process' exit code is 'exited' and its exit status is 1.
  598. Feb 21 16:30:58 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
  599. -- Subject: Unit failed
  600. -- Defined-By: systemd
  601. -- Support: https://www.debian.org/support
  602. --
  603. -- The unit smbd.service has entered the 'failed' state with result 'exit-code'.
  604. Feb 21 16:30:58 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
  605. -- Subject: A start job for unit smbd.service has failed
  606. -- Defined-By: systemd
  607. -- Support: https://www.debian.org/support
  608. --
  609. -- A start job for unit smbd.service has finished with a failure.
  610. --
  611. -- The job identifier is 826 and the job result is failed.
  612. Feb 21 16:30:58 HomeServer systemd[1]: run-rd4cb895e9b5b47d7821163b6966fb5b5.scope: Succeeded.
  613. -- Subject: Unit succeeded
  614. -- Defined-By: systemd
  615. -- Support: https://www.debian.org/support
  616. --
  617. -- The unit run-rd4cb895e9b5b47d7821163b6966fb5b5.scope has successfully entered the 'dead' state.
  618. Feb 21 16:30:58 HomeServer systemd[1]: Started /bin/systemctl stop smbd.service.
  619. -- Subject: A start job for unit run-rbba79ac16ef14f5a8b109997815245fb.scope has finished successfully
  620. -- Defined-By: systemd
  621. -- Support: https://www.debian.org/support
  622. --
  623. -- A start job for unit run-rbba79ac16ef14f5a8b109997815245fb.scope has finished successfully.
  624. --
  625. -- The job identifier is 919.
  626. Feb 21 16:30:58 HomeServer systemd[1]: run-rbba79ac16ef14f5a8b109997815245fb.scope: Succeeded.
  627. -- Subject: Unit succeeded
  628. -- Defined-By: systemd
  629. -- Support: https://www.debian.org/support
  630. --
  631. -- The unit run-rbba79ac16ef14f5a8b109997815245fb.scope has successfully entered the 'dead' state.
  632. Feb 21 16:30:58 HomeServer systemd[1]: Started /bin/systemctl start smbd.service.
  633. -- Subject: A start job for unit run-r24b9270883394ebc95837a5428934677.scope has finished successfully
  634. -- Defined-By: systemd
  635. -- Support: https://www.debian.org/support
  636. --
  637. -- A start job for unit run-r24b9270883394ebc95837a5428934677.scope has finished successfully.
  638. --
  639. -- The job identifier is 925.
  640. Feb 21 16:30:58 HomeServer systemd[1]: Starting Samba SMB Daemon...
  641. -- Subject: A start job for unit smbd.service has begun execution
  642. -- Defined-By: systemd
  643. -- Support: https://www.debian.org/support
  644. --
  645. -- A start job for unit smbd.service has begun execution.
  646. --
  647. -- The job identifier is 929.
  648. Feb 21 16:30:59 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
  649. -- Subject: Unit process exited
  650. -- Defined-By: systemd
  651. -- Support: https://www.debian.org/support
  652. --
  653. -- An ExecStart= process belonging to unit smbd.service has exited.
  654. --
  655. -- The process' exit code is 'exited' and its exit status is 1.
  656. Feb 21 16:30:59 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
  657. -- Subject: Unit failed
  658. -- Defined-By: systemd
  659. -- Support: https://www.debian.org/support
  660. --
  661. -- The unit smbd.service has entered the 'failed' state with result 'exit-code'.
  662. Feb 21 16:30:59 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
  663. -- Subject: A start job for unit smbd.service has failed
  664. -- Defined-By: systemd
  665. -- Support: https://www.debian.org/support
  666. --
  667. -- A start job for unit smbd.service has finished with a failure.
  668. --
  669. -- The job identifier is 929 and the job result is failed.
  670. Feb 21 16:30:59 HomeServer systemd[1]: run-r24b9270883394ebc95837a5428934677.scope: Succeeded.
  671. -- Subject: Unit succeeded
  672. -- Defined-By: systemd
  673. -- Support: https://www.debian.org/support
  674. --
  675. -- The unit run-r24b9270883394ebc95837a5428934677.scope has successfully entered the 'dead' state.
  676. Feb 21 16:30:59 HomeServer systemd[1]: Started /bin/systemctl start wsdd.service.
  677. -- Subject: A start job for unit run-r9aea5be2e24e41f49f2c43837b1def89.scope has finished successfully
  678. -- Defined-By: systemd
  679. -- Support: https://www.debian.org/support
  680. --
  681. -- A start job for unit run-r9aea5be2e24e41f49f2c43837b1def89.scope has finished successfully.
  682. --
  683. -- The job identifier is 1022.
  684. Feb 21 16:30:59 HomeServer systemd[1]: Starting Samba SMB Daemon...
  685. -- Subject: A start job for unit smbd.service has begun execution
  686. -- Defined-By: systemd
  687. -- Support: https://www.debian.org/support
  688. --
  689. -- A start job for unit smbd.service has begun execution.
  690.  
  691. -- The unit run-r9aea5be2e24e41f49f2c43837b1def89.scope has successfully entered the 'dead' state.
  692. Feb 21 16:30:59 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
  693. -- Subject: Unit process exited
  694. -- Defined-By: systemd
  695. -- Support: https://www.debian.org/support
  696. --
  697. -- An ExecStart= process belonging to unit smbd.service has exited.
  698. --
  699. -- The process' exit code is 'exited' and its exit status is 1.
  700. Feb 21 16:30:59 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
  701. -- Subject: Unit failed
  702. -- Defined-By: systemd
  703. -- Support: https://www.debian.org/support
  704. --
  705. -- The unit smbd.service has entered the 'failed' state with result 'exit-code'.
  706. Feb 21 16:30:59 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
  707. -- Subject: A start job for unit smbd.service has failed
  708. -- Defined-By: systemd
  709. -- Support: https://www.debian.org/support
  710. --
  711. -- A start job for unit smbd.service has finished with a failure.
  712. --
  713. -- The job identifier is 1113 and the job result is failed.
  714. Feb 21 16:30:59 HomeServer systemd[1]: Stopping Web Services Dynamic Discovery host daemon...
  715. -- Subject: A stop job for unit wsdd.service has begun execution
  716. -- Defined-By: systemd
  717. -- Support: https://www.debian.org/support
  718. --
  719. -- A stop job for unit wsdd.service has begun execution.
  720. --
  721. -- The job identifier is 1120.
  722. Feb 21 16:30:59 HomeServer systemd[1]: wsdd.service: Main process exited, code=killed, status=15/TERM
  723. -- Subject: Unit process exited
  724. -- Defined-By: systemd
  725. -- Support: https://www.debian.org/support
  726. --
  727. -- An ExecStart= process belonging to unit wsdd.service has exited.
  728. --
  729. -- The process' exit code is 'killed' and its exit status is 15.
  730. Feb 21 16:30:59 HomeServer systemd[1]: wsdd.service: Succeeded.
  731. -- Subject: Unit succeeded
  732. -- Defined-By: systemd
  733. -- Support: https://www.debian.org/support
  734. --
  735. -- The unit wsdd.service has successfully entered the 'dead' state.
  736. Feb 21 16:30:59 HomeServer systemd[1]: Stopped Web Services Dynamic Discovery host daemon.
  737. -- Subject: A stop job for unit wsdd.service has finished
  738. -- Defined-By: systemd
  739. -- Support: https://www.debian.org/support
  740. --
  741. -- A stop job for unit wsdd.service has finished.
  742. --
  743. -- The job identifier is 1120 and the job result is done.
  744. Feb 21 16:31:02 HomeServer kernel: perf: interrupt took too long (4236 > 4185), lowering kernel.perf_event_max_sample_rate to 47000
  745. Feb 21 16:31:09 HomeServer kernel: perf: interrupt took too long (5338 > 5295), lowering kernel.perf_event_max_sample_rate to 37250
  746. Feb 21 16:31:17 HomeServer kernel: perf: interrupt took too long (6679 > 6672), lowering kernel.perf_event_max_sample_rate to 29750
  747. Feb 21 16:31:30 HomeServer kernel: perf: interrupt took too long (8369 > 8348), lowering kernel.perf_event_max_sample_rate to 23750
  748. Feb 21 16:31:34 HomeServer sshd[5415]: Accepted password for root from 192.168.0.209 port 9550 ssh2
  749. Feb 21 16:31:34 HomeServer sshd[5415]: pam_unix(sshd:session): session opened for user root by (uid=0)
  750. Feb 21 16:31:48 HomeServer kernel: perf: interrupt took too long (10478 > 10461), lowering kernel.perf_event_max_sample_rate to 19000
  751. Feb 21 16:32:38 HomeServer kernel: perf: interrupt took too long (13111 > 13097), lowering kernel.perf_event_max_sample_rate to 15250
  752. Feb 21 16:33:50 HomeServer kernel: perf: interrupt took too long (16391 > 16388), lowering kernel.perf_event_max_sample_rate to 12000
  753. Feb 21 16:33:56 HomeServer anacron[469]: Job `cron.daily' started
  754. Feb 21 16:33:56 HomeServer anacron[5654]: Updated timestamp for job `cron.daily' to 2022-02-21
  755. Feb 21 16:37:50 HomeServer systemd[1]: run-docker-runtime\x2drunc-moby-bf7e0e29d88d5333baea02e31ae253d8b7e2654edcc5fe1c2ee4843207592972-runc.zHt3kz.mount: Succeeded.
  756. -- Subject: Unit succeeded
  757. -- Defined-By: systemd
  758. -- Support: https://www.debian.org/support
  759. --
  760. -- The unit run-docker-runtime\x2drunc-moby-bf7e0e29d88d5333baea02e31ae253d8b7e2654edcc5fe1c2ee4843207592972-runc.zHt3kz.mount has successfully entered the 'dead' state.
  761. Feb 21 16:39:01 HomeServer CRON[6070]: pam_unix(cron:session): session opened for user root by (uid=0)
  762. Feb 21 16:39:01 HomeServer CRON[6071]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
  763. Feb 21 16:39:01 HomeServer CRON[6070]: pam_unix(cron:session): session closed for user root
  764. Feb 21 16:39:06 HomeServer systemd[1]: Starting Clean php session files...
  765. -- Subject: A start job for unit phpsessionclean.service has begun execution
  766. -- Defined-By: systemd
  767. -- Support: https://www.debian.org/support
  768. --
  769. -- A start job for unit phpsessionclean.service has begun execution.
  770. --
  771. -- The job identifier is 1121.
  772. Feb 21 16:39:07 HomeServer systemd[1]: phpsessionclean.service: Succeeded.
  773. -- Subject: Unit succeeded
  774. -- Defined-By: systemd
  775. -- Support: https://www.debian.org/support
  776. --
  777. -- The unit phpsessionclean.service has successfully entered the 'dead' state.
  778. Feb 21 16:39:07 HomeServer systemd[1]: Started Clean php session files.
  779. -- Subject: A start job for unit phpsessionclean.service has finished successfully
  780. -- Defined-By: systemd
  781. -- Support: https://www.debian.org/support
  782. --
  783. -- A start job for unit phpsessionclean.service has finished successfully.
  784. --
  785. -- The job identifier is 1121.
  786. Feb 21 16:39:43 HomeServer login[634]: pam_unix(login:auth): check pass; user unknown
  787. Feb 21 16:39:43 HomeServer login[634]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=/dev/tty1 ruser= rhost=
  788. Feb 21 16:39:46 HomeServer login[634]: FAILED LOGIN (1) on '/dev/tty1' FOR 'UNKNOWN', Authentication failure
  789. Feb 21 16:39:53 HomeServer login[634]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
  790. Feb 21 16:39:53 HomeServer login[6197]: ROOT LOGIN on '/dev/tty1'
  791. Feb 21 16:41:52 HomeServer sudo[7545]: root : TTY=tty1 ; PWD=/root ; USER=root ; COMMAND=/usr/sbin/service smbd restart
  792. Feb 21 16:41:52 HomeServer sudo[7545]: pam_unix(sudo:session): session opened for user root by root(uid=0)
  793. Feb 21 16:41:52 HomeServer systemd[1]: Starting Samba SMB Daemon...
  794. -- Subject: A start job for unit smbd.service has begun execution
  795. -- Defined-By: systemd
  796. -- Support: https://www.debian.org/support
  797. --
  798. -- A start job for unit smbd.service has begun execution.
  799. --
  800. -- The job identifier is 1208.
  801. Feb 21 16:41:55 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
  802. -- Subject: Unit process exited
  803. -- Defined-By: systemd
  804. -- Support: https://www.debian.org/support
  805.  
  806. -- An ExecStart= process belonging to unit smbd.service has exited.
  807. --
  808. -- The process' exit code is 'exited' and its exit status is 1.
  809. Feb 21 16:41:55 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
  810. -- Subject: Unit failed
  811. -- Defined-By: systemd
  812. -- Support: https://www.debian.org/support
  813. --
  814. -- The unit smbd.service has entered the 'failed' state with result 'exit-code'.
  815. Feb 21 16:41:55 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
  816. -- Subject: A start job for unit smbd.service has failed
  817. -- Defined-By: systemd
  818. -- Support: https://www.debian.org/support
  819. --
  820. -- A start job for unit smbd.service has finished with a failure.
  821. --
  822. -- The job identifier is 1208 and the job result is failed.
  823. Feb 21 16:41:55 HomeServer sudo[7545]: pam_unix(sudo:session): session closed for user root
  824. Feb 21 16:43:48 HomeServer systemd[1]: Starting Cleanup of Temporary Directories...
  825. -- Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution
  826. -- Defined-By: systemd
  827. -- Support: https://www.debian.org/support
  828. --
  829. -- A start job for unit systemd-tmpfiles-clean.service has begun execution.
  830. --
  831. -- The job identifier is 1301.
  832. Feb 21 16:43:48 HomeServer systemd-tmpfiles[7982]: [/usr/lib/tmpfiles.d/fail2ban-tmpfiles.conf:1] Line references path below legacy directory /var/run/, updating /var/run/fail2ban → /run/fail2ban; please update the tmpfiles.d/ drop-
  833. Feb 21 16:43:48 HomeServer systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
  834. -- Subject: Unit succeeded
  835. -- Defined-By: systemd
  836. -- Support: https://www.debian.org/support
  837. --
  838. -- The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state.
  839. Feb 21 16:43:48 HomeServer systemd[1]: Started Cleanup of Temporary Directories.
  840. -- Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully
  841. -- Defined-By: systemd
  842. -- Support: https://www.debian.org/support
  843. --
  844. -- A start job for unit systemd-tmpfiles-clean.service has finished successfully.
  845.  
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!