Arch32.service fails on start. bundled 32bit system

AcousticBruce · 2015-05-22 18:46:18

I am using the install bundled 32bit system in 64bit system wiki and I think I am having trouble in the systemd service part.

I am getting an error starting the arch32 service with systemctl. I have looked at the error messages and I am just not sure what is wrong here. Can someone point out what the error message is telling me, so that I can, in the future, read error messages better? I have did searches and google came up short. I am an eager Linux student. I would more than appreaciate any "hints" so that I can become better and be more value as I help others. Thank you.

systemctl start arch32
## Job for arch32.service failed. See "systemctl status arch32.service" and "journalctl -xe" for details.

The result of systemct status message...

# systemctl status -l arch32
● arch32.service - 32-bit chroot
   Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2015-05-22 10:32:54 EDT; 8min ago
  Process: 980 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
 Main PID: 980 (code=exited, status=1/FAILURE)

May 22 10:32:53 archhost systemd[1]: Starting 32-bit chroot...
May 22 10:32:54 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 22 10:32:54 archhost systemd[1]: Failed to start 32-bit chroot.
May 22 10:32:54 archhost systemd[1]: Unit arch32.service entered failed state.
May 22 10:32:54 archhost systemd[1]: arch32.service failed.

The result of jouornalctl message...

# journalctl -xe
May 23 07:41:27 archhost org.a11y.Bus[3104]: Activating service name='org.a11y.atspi.Registry'
May 23 07:41:28 archhost org.a11y.Bus[3104]: Successfully activated service 'org.a11y.atspi.Registry'
May 23 07:41:28 archhost org.a11y.atspi.Registry[3233]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
May 23 07:41:28 archhost polkitd[3111]: Registered Authentication Agent for unix-session:c1 (system bus name :1.13 [/usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd0
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x187
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x188
May 23 07:41:32 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x187
May 23 07:41:33 archhost kernel: dell_wmi: Unknown WMI event type 0x11: 0x188
May 23 07:49:50 archhost sudo[3422]: codeamend : TTY=pts/0 ; PWD=/usr/local/bin ; USER=root ; COMMAND=/usr/bin/systemctl start arch32
May 23 07:49:50 archhost sudo[3422]: pam_unix(sudo:session): session opened for user root by codeamend(uid=0)
May 23 07:49:50 archhost polkitd[3111]: Registered Authentication Agent for unix-process:3423:70961 (system bus name :1.14 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 23 07:49:50 archhost systemd[1]: Starting 32-bit chroot...
-- Subject: Unit arch32.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit arch32.service has begun starting up.
May 23 07:49:50 archhost arch32[3428]: mount: mount point /opt/arch32/scratch does not exist
May 23 07:49:50 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 23 07:49:50 archhost systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit arch32.service has failed.
-- 
-- The result is failed.
May 23 07:49:50 archhost systemd[1]: Unit arch32.service entered failed state.
May 23 07:49:50 archhost systemd[1]: arch32.service failed.
May 23 07:49:50 archhost sudo[3422]: pam_unix(sudo:session): session closed for user root
May 23 07:49:50 archhost polkitd[3111]: Unregistered Authentication Agent for unix-process:3423:70961 (system bus name :1.14, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
May 23 07:53:11 archhost systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-tmpfiles-clean.service has begun starting up.
May 23 07:53:11 archhost systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-tmpfiles-clean.service has finished starting up.
-- 
-- The start-up result is done.

Last edited by AcousticBruce (2015-05-23 15:57:21)

nomorewindows · 2015-05-22 18:58:26

What does your arch32.service look like? Did you or it mount proc, sys, dev?

AcousticBruce · 2015-05-22 19:26:59

nomorewindows wrote:

What does your arch32.service look like? Did you or it mount proc, sys, dev?

Nomorewindows ( I like the name. I just got rid of windows also. ) I am not sure what you mean by mount proc, sys, dev. I do have a proc, sys, and dev folder in my /opt/arch32 directory, if that is what you are asking. Can you help me figure out what you are asking?

My /etc/systemd/system/arch32.service file....

GNU nano 2.4.1            File: arch32.service                                

[Unit]
Description=32-bit chroot

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/local/bin/arch32 start
ExecStop=/usr/local/bin/arch32 stop

[Install]
WantedBy=multi-user.target

nomorewindows · 2015-05-23 13:02:13

Ok, so now what does the /usr/local/bin/arch32 look like?

AcousticBruce · 2015-05-23 15:47:00

Basically both of these are a copy from the wiki. I did not modify them. Well... not on purpose anyway.

BTW... I also edited my journalctl -xe in my original post. I redirected the output to a file and copied and pasted it. I realized some of it was cut off because my console was not set to word-wrap. So I updated it.

/usr/local/bin/arch32:

#!/bin/bash

## User variables.
MOUNTPOINT=/opt/arch32

## Set MANAGEPARTITION to any value if /opt/arch32 resides on a separate
## partition and not mounted by /etc/fstab or some other means.
## If /opt/arch32 is part of your rootfs, leave this empty.
MANAGEPARTITION=

## Leave USEDISTCC empty unless you wish to use distccd from within the chroot.
USEDISTCC=
DISTCC_SUBNET='10.9.8.0/24'

## PIDFILE shouldn't need to ba changed from this default.
PIDFILE=/run/arch32

start_distccd() {
	[[ ! -L "$MOUNTPOINT"/usr/bin/distccd-chroot ]] &&
		ln -s /usr/bin/distccd "$MOUNTPOINT"/usr/bin/distccd-chroot 
	DISTCC_ARGS="--user nobody --allow $DISTCC_SUBNET --port 3692 --log-level warning --log-file /tmp/distccd-i686.log"

	[[ -z "$(pgrep distccd-chroot)" ]] &&
		linux32 chroot "$MOUNTPOINT" /bin/bash -c "/usr/bin/distccd-chroot --daemon $DISTCC_ARGS"
}

stop_distccd() {
	[[ -n "$(pgrep distccd-chroot)" ]] &&
		linux32 chroot "$MOUNTPOINT" /bin/bash -c "pkill -SIGTERM distccd-chroot"
}

case $1 in
	start)
		[[ -f "$PIDFILE" ]] && exit 1

		if [[ -n "$MANAGEPARTITION" ]]; then
			mountpoint -q $MOUNTPOINT || mount LABEL="arch32" $MOUNTPOINT
		fi

		dirs=(/tmp /dev /dev/pts /home /scratch)
		for d in "${dirs[@]}"; do
			mount -o bind $d "$MOUNTPOINT"$d
		done

		mount -t proc none "$MOUNTPOINT/proc"
		mount -t sysfs none "$MOUNTPOINT/sys"
		touch "$PIDFILE"
		[[ -n "$USEDISTCC" ]] && start_distccd
		;;

	stop)
		[[ ! -f "$PIDFILE" ]] && exit 1
		[[ -n "$USEDISTCC" ]] && stop_distccd

		if [[ -n "$MANAGEPARTITION" ]]; then
			umount -R -A -l "$MOUNTPOINT"
		else
			dirs=(/home /dev/pts /dev /tmp /scratch)
			[[ -n "$USEDISTCC" ]] && stop_distccd
			umount "$MOUNTPOINT"/{sys,proc}
			for d in "${dirs[@]}"; do
				umount -l "$MOUNTPOINT$d"
			done
		fi
		
		rm -f "$PIDFILE"
		;;
	*)
		echo "usage: $0 (start|stop)"
		exit 1
esac

Last edited by AcousticBruce (2015-05-23 16:13:26)

nomorewindows · 2015-05-23 15:51:43

Looks ok, try running arch32 from root and see what it tells you (that systemd sort of hides).

AcousticBruce · 2015-05-23 16:14:20

I updated my journal -xe in the first post. Some was cut off before.

All of this was ran from su.

Last edited by AcousticBruce (2015-05-23 16:16:02)

Head_on_a_Stick · 2015-05-23 16:21:49

The guide you are following is pretty old.

Have you tried systemd-nspawn?
https://wiki.archlinux.org/index.php/Systemd-nspawn

I have used it to create a 32-bit (Debian) chroot system for my 64-bit machine with good results.

AcousticBruce · 2015-05-24 14:51:41

Head_on_a_Stick wrote:

The guide you are following is pretty old.
Have you tried systemd-nspawn?
https://wiki.archlinux.org/index.php/Systemd-nspawn
I have used it to create a 32-bit (Debian) chroot system for my 64-bit machine with good results.

This looks very interesting and actually easier. Ill give it a shot and reply back or marked solved. Thanks

Last edited by AcousticBruce (2015-05-24 14:52:07)

graysky · 2015-05-24 14:55:20

Edit your /usr/local/bin/arch32 script removing the reference to '/scratch' unless you actually have it on your system. That was a typo from me on the wiki which has now been corrected.

Last edited by graysky (2015-05-24 14:56:05)

AcousticBruce · 2015-05-24 17:04:03

graysky wrote:

Edit your /usr/local/bin/arch32 script removing the reference to '/scratch' unless you actually have it on your system. That was a typo from me on the wiki which has now been corrected.

I removed the /scratch from two areas and made a copy of the wiki version just in case I was wrong. I still got these errors.

$ systemctl status -l arch32.service
● arch32.service - 32-bit chroot
   Loaded: loaded (/etc/systemd/system/arch32.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2015-05-24 08:53:49 EDT; 20s ago
  Process: 2139 ExecStart=/usr/local/bin/arch32 start (code=exited, status=1/FAILURE)
 Main PID: 2139 (code=exited, status=1/FAILURE)

May 24 08:53:49 archhost systemd[1]: Starting 32-bit chroot...
May 24 08:53:49 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 24 08:53:49 archhost systemd[1]: Failed to start 32-bit chroot.
May 24 08:53:49 archhost systemd[1]: Unit arch32.service entered failed state.
May 24 08:53:49 archhost systemd[1]: arch32.service failed

$ journalctl -xe
-- Unit arch32.service has begun starting up.
May 24 08:49:36 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 24 08:49:36 archhost systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit arch32.service has failed.
-- 
-- The result is failed.
May 24 08:49:36 archhost polkitd[663]: Unregistered Authentication Agent for unix-process:2103:877657 (system bus name :1.20, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
May 24 08:49:36 archhost systemd[1]: Unit arch32.service entered failed state.
May 24 08:49:36 archhost systemd[1]: arch32.service failed.
May 24 08:53:45 archhost polkitd[663]: Registered Authentication Agent for unix-process:2132:902936 (system bus name :1.24 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 24 08:53:49 archhost polkitd[663]: Operator of unix-session:c1 successfully authenticated as unix-user:codeamend to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.25 [systemctl start arch32] (owned by unix-user:codeamend)
May 24 08:53:49 archhost systemd[1]: Starting 32-bit chroot...
-- Subject: Unit arch32.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit arch32.service has begun starting up.
May 24 08:53:49 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 24 08:53:49 archhost systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit arch32.service has failed.
-- 
-- The result is failed.
May 24 08:53:49 archhost systemd[1]: Unit arch32.service entered failed state.
May 24 08:53:49 archhost systemd[1]: arch32.service failed.
May 24 08:53:49 archhost polkitd[663]: Unregistered Authentication Agent for unix-process:2132:902936 (system bus name :1.24, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
May 24 08:56:04 archhost sudo[2156]: codeamend : TTY=pts/2 ; PWD=/opt/arch32/usr/local/bin ; USER=root ; COMMAND=/usr/bin/nano arch32
May 24 08:56:04 archhost sudo[2156]: pam_unix(sudo:session): session opened for user root by codeamend(uid=0)
May 24 08:56:21 archhost sudo[2156]: pam_unix(sudo:session): session closed for user root
May 24 08:56:24 archhost polkitd[663]: Registered Authentication Agent for unix-process:2160:918835 (system bus name :1.28 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
May 24 08:56:28 archhost polkitd[663]: Operator of unix-session:c1 successfully authenticated as unix-user:codeamend to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.29 [systemctl start arch32] (owned by unix-user:codeamend)
May 24 08:56:28 archhost systemd[1]: Starting 32-bit chroot...
-- Subject: Unit arch32.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit arch32.service has begun starting up.
May 24 08:56:28 archhost systemd[1]: arch32.service: main process exited, code=exited, status=1/FAILURE
May 24 08:56:28 archhost systemd[1]: Failed to start 32-bit chroot.
-- Subject: Unit arch32.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit arch32.service has failed.
-- 
-- The result is failed.
May 24 08:56:28 archhost systemd[1]: Unit arch32.service entered failed state.
May 24 08:56:28 archhost systemd[1]: arch32.service failed.
May 24 08:56:28 archhost polkitd[663]: Unregistered Authentication Agent for unix-process:2160:918835 (system bus name :1.28, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

nomorewindows · 2015-05-24 19:38:23

command=/usr/bin/nano arch32

?
It is trying to call nano apparently instead of arch32.
All you would need is to mount the api filesystems, and then chroot the root of the directory, and the kernel is smart enough to know it's a different architecture.

AcousticBruce · 2015-05-24 21:06:18

nomorewindows wrote:

command=/usr/bin/nano arch32
?
It is trying to call nano apparently instead of arch32.
All you would need is to mount the api filesystems, and then chroot the root of the directory, and the kernel is smart enough to know it's a different architecture.

Shouldnt it be /usr/local/bin ????

I am not sure what you mean by mounting the api file systems and then chroot. I know how to chroot (mount system here) $SHELL. I figued when you run chroot you have to add the mounting point and that is when the fs is loaded. Just trying to get further understanding and semantics are important to me for learning. Chroot has succesfully worked and always has. I am just confused as to what the whole systemd service part is for.

Last edited by AcousticBruce (2015-05-24 21:08:40)

AcousticBruce · 2015-05-24 21:25:53

I guess the kernal was not smart enough basically during a pacman package sync I got an error that siad "invalid architecture". My mirrorlist in the pacman.d directory is for i686.

Last edited by AcousticBruce (2015-05-24 21:26:28)

nomorewindows · 2015-05-24 21:40:34

I always have to

pacman -Syu --config etc/pacman.conf --arch=i686 -r /wherever/32-bit/chroot/is/located

.
It will use the mirrorlist of the host.

Last edited by nomorewindows (2015-05-24 21:41:19)

Arch Linux

#1 2015-05-22 18:46:18

Arch32.service fails on start. bundled 32bit system

#2 2015-05-22 18:58:26

Re: Arch32.service fails on start. bundled 32bit system

#3 2015-05-22 19:26:59

Re: Arch32.service fails on start. bundled 32bit system

#4 2015-05-23 13:02:13

Re: Arch32.service fails on start. bundled 32bit system

#5 2015-05-23 15:47:00

Re: Arch32.service fails on start. bundled 32bit system

#6 2015-05-23 15:51:43

Re: Arch32.service fails on start. bundled 32bit system

#7 2015-05-23 16:14:20

Re: Arch32.service fails on start. bundled 32bit system

#8 2015-05-23 16:21:49

Re: Arch32.service fails on start. bundled 32bit system

#9 2015-05-24 14:51:41

Re: Arch32.service fails on start. bundled 32bit system

#10 2015-05-24 14:55:20

Re: Arch32.service fails on start. bundled 32bit system

#11 2015-05-24 17:04:03

Re: Arch32.service fails on start. bundled 32bit system

#12 2015-05-24 19:38:23

Re: Arch32.service fails on start. bundled 32bit system

#13 2015-05-24 21:06:18

Re: Arch32.service fails on start. bundled 32bit system

#14 2015-05-24 21:25:53

Re: Arch32.service fails on start. bundled 32bit system

#15 2015-05-24 21:40:34

Re: Arch32.service fails on start. bundled 32bit system

Board footer