Debian Upgrade Buster To Bullseye - Revision history

MkWikiEnSysOp: /* scanimage exits with "Out of memory" error */ Add Using scanimage in the chroot environment by unprivileged users

2022-10-28T21:05:11Z

scanimage exits with "Out of memory" error: Add Using scanimage in the chroot environment by unprivileged users

← Older revision		Revision as of 21:05, 28 October 2022
Line 54:		Line 54:
	echo "LANG=en_US.UTF-8" >> /etc/profile		echo "LANG=en_US.UTF-8" >> /etc/profile
	apt install sane-utils		apt install sane-utils

			=== Using scanimage in the chroot environment by unprivileged users ===

			For this purpose I wrote a small program named [https://gitlab.com/MichaelKremser/chroot_scanimage/-/tree/master/ chroot_scanimage].

	[[Category:Linux]]		[[Category:Linux]]

MkWikiEnSysOp at 13:15, 9 October 2022

2022-10-09T13:15:02Z

← Older revision		Revision as of 13:15, 9 October 2022
Line 11:		Line 11:
	</pre>		</pre>

	<code>journalctl -xe</code> contains relevant information:		<code>journalctl -xe -u isc-dhcp-server</code> contains relevant information:

	<pre>		<pre>

MkWikiEnSysOp: +scanimage exits with "Out of memory" error

2022-10-01T20:34:45Z

+scanimage exits with "Out of memory" error

@@ Line 33: / Line 33: @@
+}
 </pre>
 [[Category:Linux]]

MkWikiEnSysOp: Created page with "This article contains all problems that I encountered when upgrading Debian from 10/Buster to 11/Bullseye. == isc-dhcp-server failed to start == Unfortunately, all you see a..."

2022-10-01T10:52:28Z

Created page with "This article contains all problems that I encountered when upgrading Debian from 10/Buster to 11/Bullseye. == isc-dhcp-server failed to start == Unfortunately, all you see a..."

New page

This article contains all problems that I encountered when upgrading Debian from 10/Buster to 11/Bullseye.

== isc-dhcp-server failed to start ==

Unfortunately, all you see at first using <code>systemctl status isc-dhcp-server</code> is

<pre>
Sep 30 20:51:28 host systemd[1]: isc-dhcp-server.service: Control process exited, code=exited, status=1/FAILURE
Sep 30 20:51:28 host systemd[1]: isc-dhcp-server.service: Failed with result 'exit-code'.
Sep 30 20:51:28 host systemd[1]: Failed to start LSB: DHCP server.
</pre>

<code>journalctl -xe</code> contains relevant information:

<pre>
Okt 01 09:22:26 host dhcpd[47376]: Server starting service.
Okt 01 09:22:28 host isc-dhcp-server[47361]: Starting ISC DHCPv4 server: dhcpd.
Okt 01 09:22:28 host isc-dhcp-server[47361]: Launching IPv6 server only.
Okt 01 09:22:28 host dhcpd[47388]: Wrote 0 NA, 0 TA, 0 PD leases to lease file.
Okt 01 09:22:28 host dhcpd[47388]:
Okt 01 09:22:28 host dhcpd[47388]: No subnet6 declaration for vmnet (2001:0DB8::/32).
Okt 01 09:22:28 host dhcpd[47388]: ** Ignoring requests on vmnet. If this is not what
Okt 01 09:22:28 host dhcpd[47388]: you want, please write a subnet6 declaration
Okt 01 09:22:28 host dhcpd[47388]: in your dhcpd.conf file for the network segment
Okt 01 09:22:28 host dhcpd[47388]: to which interface vmnet is attached. **
</pre>

The simple solution is to add the required subnet declaration in <code>/etc/dhcp/dhcpd6.conf</code>:

<pre>
subnet6 2001:0DB8::/32 {
range6 2001:0DB8::1 2001:0DB8::efff;
}
</pre>

[[Category:Linux]]