Re: iSCSI LUN mount on boot
Claudio Jeker writes:
> Yeah, the documentation is not great.
>
> You need to add 'net' to the mount options in /etc/fstab for iscsi drives.
> Then our rc script will do the right thing and mount these drives late
> (after iscsid started).
>
> .a /mnt/test ffs rw,noatime,nodev,nosuid,net 1 2
>
> With that it should work. You can not use iscsi for /, /usr, /var but it
> works for /home or /var/www.
Thanks Claudio for the note. Unfortunately, this was not
successful. Slightly different, but ultimately the same problem.
When the machine comes up, it does indeed pass mounting all of the local
partitions before trying to mount the iSCSI target.
However, it still blows up and enters single user mode. Upon entering
single user mode, the additional NIC that connects to the SAN does
appear to be configured and happy (I can ping the iSCSI host). You can
see pictures of the screen before [1] and after [2] entering and exiting
single user mode. In [3], you can see the machine does eventually hit a
login prompt.
Upon exiting single user mode, it then gives an error message that
"SIOCSIFGATTR" is an invalid argument to ifconfig, before continuing to
boot. It then says iscsid failed to start. This is visible in [2] and [3].
Once actually logged in, it appears as though iscsid is dead in the
water. However, if I remove the /etc/fstab entry, it boots as normal and
then I can mount manually as expected. Very strange.
Checking /var/log/daemon, this is what I see:
Feb 20 18:59:28 elara iscsid[52173]: startup
Feb 20 18:59:28 elara iscsid[52173]: fatal in iscsid: vscsi_open: Device busy
Diagnostic info to follow. dmesg is also attached.
I'm wondering if this is a misconfiguration on my part, or more
potentially is it a bug? This is on a fresh install of today's -current
snapshot - I'm rebuilding the machine due to hardware failure/upgrades
and can't say I've actually tried to do this before, so can't say it
worked before. It is just odd to me to that the drive mounts fine
manually, but blows up when trying to mount on boot.
Hopefully, somebody can provide some answers. Please let me know if any
further info is required.
Thanks,
Ash
[1] https://thalassa.fagg.id.au/IMG_6318.jpg
[2] https://thalassa.fagg.id.au/IMG_6321.jpg
[3] https://thalassa.fagg.id.au/IMG_6322.jpg
Diagnostic info:
Here is my full and complete /etc/fstab. /build is the mount-point in
question. It is my intention to (hopefully) mount it at /usr/ports, but
just for the sake of troubleshooting I tried a different mountpoint.
I also tried the exact same options Claudio suggested with the same
result.
elara$ cat /etc/fstab
02215eb188a74570.b none swap sw
02215eb188a74570.a / ffs rw 1 1
02215eb188a74570.k /home ffs rw,nodev,nosuid 1 2
02215eb188a74570.d /tmp ffs rw,nodev,nosuid 1 2
02215eb188a74570.f /usr ffs rw,nodev 1 2
02215eb188a74570.g /usr/X11R6 ffs rw,nodev 1 2
02215eb188a74570.h /usr/local ffs rw,wxallowed,nodev 1 2
02215eb188a74570.j /usr/obj ffs rw,nodev,nosuid 1 2
02215eb188a74570.i /usr/src ffs rw,nodev,nosuid 1 2
02215eb188a74570.e /var ffs rw,nodev,nosuid 1 2
08b434e6d3d1d227.c /build ffs rw,noatime,nodev,wxallowed,net 1 2
Here is my full and complete /etc/iscsid.conf:
elara$ cat /etc/iscsi.conf
target "ports" {
initiatoraddr 172.16.0.2
targetaddr 172.16.0.1
targetname "iqn.2011-01.au.id.fagg.ctl:elara-usr-ports"
}
And the two NIC configs + an ifconfig:
elara$ cat /etc/hostname.re0
inet 192.168.1.6 0xff00
elara$ cat /etc/hostname.ix0
inet 172.16.0.2 0xf000
up
elara$ doas ifconfig
doas (f...@elara.fagg.id.au) password:
lo0: flags=8049 mtu 32768
index 4 priority 0 llprio 3
groups: lo
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff00
ix0: flags=8843 mtu 1500
lladdr 90:e2:ba:29:76:a0
index 1 priority 0 llprio 3
media: Ethernet autoselect (10GSFP+Cu full-duplex,rxpause,txpause)
status: active
inet 172.16.0.2 netmask 0xf000 broadcast 172.16.15.255
re0: flags=8843 mtu 1500
lladdr 70:85:c2:67:19:b9
index 2 priority 0 llprio 3
groups: egress
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet 192.168.1.6 netmask 0xff00 broadcast 192.168.1.255
enc0: flags=0<>
index 3 priority 0 llprio 3
groups: enc
status: active
pflog0: flags=141 mtu 33136
index 5 priority 0 llprio 3
groups: pflog
dmesg attached below:
OpenBSD 6.9-beta (GENERIC.MP) #346: Fri Feb 19 23:56:21 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 42861899776 (40876MB)
avail mem = 41547546624 (39622MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xed2d0 (33 entries)
bios0: vendor American Megatrends Inc. version "P4.40" date 01/05/2018
bios0: ASRock AB350 Pro4
sndiod on by default (does it need to be ? )
Hello, I was wondering should sndiod (default) startup be determined based on whether or not it the install is a typical headless install (off) or an install for a user machine with running X is there a reason why one would need to run this daemon by default? my thinking is by having the service off by default would reduce the default attack surface of the OS ? perhaps the installer could use the answer to the question do you intend to run X to determine whether or not to enable the sndiod daemon ? I hope this helps -- Kindest regards, Tom Smyth.
pf on bridge interface not working
npppd - changing clients' route table
Hi,
I have a router with VPN server (npppd). LAN net is 10.109.3.0/24, gw
10.109.3.254, the VPN net is 10.109.4.0/24, gw 10.109.4.254.
If the client is conencted to VPN all client's traffic to 10.0.0.0/8 goes via
10.109.4.254
client> route print
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1192.168.1.101
20
10.0.0.0 255.0.0.0 10.109.4.254 10.109.4.1
21
10.109.4.1 255.255.255.255 On-link10.109.4.1276
[...]
I need to redirect the traffic to 10.109.4.254 only if it goes to the remote
LAN (10.109.3.0/24), the rest should go via def gw.
How can I configure it on the router/server side ?
$ cat /etc/npppd/npppd.conf
# $OpenBSD: npppd.conf,v 1.3 2020/01/23 03:01:22 dlg Exp $
# sample npppd configuration file. see npppd.conf(5)
set max-session 200
set user-max-session 4
authentication LOCAL type local {
users-file "/etc/npppd/npppd-users"
}
tunnel L2TP protocol l2tp {
listen on X.X.X.X
}
ipcp IPCP {
pool-address 10.109.4.1-10.109.4.32
dns-servers 1.1.1.1
}
# use pppx(4) interface. use an interface per a ppp session.
interface pppx0 address 10.109.4.254 ipcp IPCP
bind tunnel from L2TP authenticated by LOCAL to pppx0
$ cat /etc/npppd/npppd-users
rdk:\
:password=pasword:\
:framed-ip-address=10.109.4.1:
#:framed-ip-netmask=255.255.255.0:
$ dmesg | head
OpenBSD 6.8 (GENERIC.MP) #4: Mon Jan 11 10:35:56 MST 2021
r...@syspatch-68-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
--
Radek
Re: SB drive not detected after reboot on PC Engines APU2
‐‐‐ Original Message ‐‐‐
On Saturday, February 20, 2021 4:51 AM, Marcus Glocker wrote:
> On Fri, Feb 19, 2021 at 04:48:11PM +, marfabastewart wrote:
>
> > Synopsis: USB drive not detected after reboot on PC Engines APU2
> > Category: amd64
> > Environment:
> > System : OpenBSD 6.9
> > Details : OpenBSD 6.9-beta (GENERIC.MP) #343: Thu Feb 18 23:09:55 MST 2021
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > Architecture: OpenBSD.amd64
> > Machine : amd64
> > Description:
> > After leaving USB drive plugged in and then rebooting on
> > PC Engines APU2, my USB drive isn't detected. If I unplug
> > and replug into the same USB port, it doesn't change console
> > output or dmesg, even though the USB drive does get power.
> > Plugging into a different port triggers detection and the
> > drive can then be mounted. The USB drive I've tested is a
> > Western Digital Elements drive. The same thing happens on
> > multiple PC Engines APU2 units running -current for a while,
> > but unfortunately I procrastinated on reporting this. I can
> > attach the same drive to a desktop and a laptop running
> > current, and they detect it after reboot. The usbdevs
> > output below is after switching USB ports.
> > How-To-Repeat:
> > Leave USB drive in port. Reboot. Even removing and putting
> > in same port doesn't detect drive. Only switching to other
> > USB port detects drives.
> > Fix:
> > work around is put USB drive in other USB port after reboot.
>
> Is this dmesg showing the boot while the USB disk is attached?
>
> On my APU2 I see something similar, but not exactly the same. When a
> USB device is attached, the controller sometimes comes up in a non-
> halted state, and then the halt attempt fails.
>
> Controller already halted at boot, all good:
>
> xhci0 at pci0 dev 16 function 0 "AMD Bolton xHCI" rev 0x11: msi, xHCI 1.0
> halted=1
> i=0
> usb0 at xhci0: USB revision 3.0
>
> Controller not halted at boot, halt request fails/timeouts:
>
> xhci0 at pci0 dev 16 function 0 "AMD Bolton xHCI" rev 0x11: msi, xHCI 1.0
> halted=0
> i=100
> xhci0: halt timeout
> xhci0: reset timeout
> xhci0: init failed, error=5
>
> But in my case the controller attachment entirely fails, so switching
> port won't help.
>
> It might be some quirk related to the AMD Bolton xHCI controller, but
> though it looks like not exactly the same issue.
>
> You could boot again with this diff compiled in, while your USB disk
> is attached so we can get more clarity.
>
> Index: sys/dev/usb/xhci.c
>
> =
>
> RCS file: /cvs/src/sys/dev/usb/xhci.c,v
> retrieving revision 1.120
> diff -u -p -u -p -r1.120 xhci.c
> --- sys/dev/usb/xhci.c 24 Dec 2020 14:11:38 - 1.120
> +++ sys/dev/usb/xhci.c 20 Feb 2021 10:48:57 -
> @@ -560,6 +560,9 @@ xhci_reset(struct xhci_softc *sc)
> uint32_t hcr;
> int i;
>
> - hcr = XOREAD4(sc, XHCI_USBSTS) & XHCI_STS_HCH;
> - printf("halted=%d\n", hcr);
> - XOWRITE4(sc, XHCI_USBCMD, 0); /* Halt controller */
> for (i = 0; i < 100; i++) {
> usb_delay_ms(>sc_bus, 1);
>
>
> @@ -567,6 +570,7 @@ xhci_reset(struct xhci_softc *sc)
> if (hcr)
> break;
> }
>
> - printf("i=%d\n", i);
>
> if (!hcr)
> printf("%s: halt timeout\n", DEVNAME(sc));
>
Hi. The dmesg was with the USB drive attached. I
plugged it to the other USB port so it would
be detected and copied the output of sendbug.
I will apply the patch as soon as possible and
let you know. I hope to do it today.
Thanks!
(My subject line was a copy/paste fail -- I missed the
"U" in "USB" from the synopsis.)
Re: Possible omission in cflags from pkg-config freeglut
On 2021-02-19, Julian Smith wrote:
> I'm wondering whether pkg-config might not be outputing correct flags
> for freeglut.
>
> For example this programme:
>
> #include
> int main(void)
> {
> return 0;
> }
>
> - fails to build with:
> cc `pkg-config --cflags --libs freeglut` foo.c
>
> because:
>
> In file included from foo.c:1:
> In file included from /usr/local/include/GL/glut.h:17:
> /usr/local/include/GL/freeglut_std.h:143:13: fatal error: 'GL/gl.h' file
> not found
> # include
> ^
> 1 error generated.
>
> But it builds ok if we add /usr/X11R6/include to the include path:
>
> cc `pkg-config --cflags --libs freeglut` -I/usr/X11R6/include foo.c
>
>
> For me, "pkg-config --cflags --libs freeglut" outputs:
>
> -I/usr/local/include -L/usr/local/lib -lglut
>
> So should pkg-config also output "-I/usr/X11R6/include" in this case?
>
>
> I'm running OpenBSD 6.8 GENERIC.MP#98 amd64
>
>
> Thanks for any clarification,
>
> - Jules
>
Yes that will need adding to the freeglut port. Should be easy
enough, send diffs to ports@ or ask for help there.
baresip-gtk
Hello, How do you use baresip-gtk? I have module_app gtk.so uncommented, but nothing happens. Thanks. -- With best regards, Gregory Edigarov
Re: No advertisements from CARP master
On 2021-02-20, Dev Op wrote: > Hello, collegues! > > In vlan2 I have 4 routers: rt1 (master) and rt2 (slave) grouped into VHID > 50 in terms of CARP; rt3 (master) and rt4 (slave) grouped into VHID 2. Why > don't I see carp advertisements from rt1? Instead, I see carp announcements > only from rt3 (vhid2). Where am I wrong? > > rt1: > > -> % ifconfig carp2 | grep -v inet > carp2: flags=8843 mtu 1500 > lladdr 00:00:5e:00:01:32 > description: Interlink > index 5 priority 15 llprio 3 > carp: MASTER carpdev vlan2 vhid 50 advbase 1 advskew 0 > groups: carp > status: master > ks1@rt1 [05:44:47] [~] > -> % sudo tcpdump -c 10 -ni carp2 proto carp > tcpdump: listening on carp2, link-type EN10MB > 05:44:54.003157 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > 05:44:55.003217 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > 05:44:56.003236 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > 05:44:57.003276 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > 05:44:58.003313 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > 05:44:59.003354 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > 05:45:00.003398 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > 05:45:01.003431 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > 05:45:02.003475 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > 05:45:03.003512 CARPv2-advertise 36: vhid=2 advbase=1 advskew=0 demote=0 > (DF) [tos 0x10] > ks1@rt1 [05:45:03] [~] > -> % sysctl net.inet.carp > net.inet.carp.allow=1 > net.inet.carp.preempt=1 > net.inet.carp.log=2 > ks1@rt1 [05:46:40] [~] > -> % uname -r > 6.8 > ks1@rt1 [05:57:11] [~] > -> % sudo sysctl net.inet.carp.log=7 > net.inet.carp.log: 2 -> 7 > ks1@rt1 [05:57:25] [~] > -> % tail -f /var/log/messages > Feb 20 05:57:57 border1 /bsd: carp2: ip_output failed: 13 > Feb 20 05:57:58 border1 /bsd: carp2: ip_output failed: 13 > Feb 20 05:57:59 border1 /bsd: carp2: ip_output failed: 13 > Feb 20 05:58:00 border1 /bsd: carp2: ip_output failed: 13 > Feb 20 05:58:01 border1 /bsd: carp2: ip_output failed: 13 > ... $ grep 13 /usr/include/sys/errno.h #define EACCES 13 /* Permission denied */ Check that your PF rules allow sending carp's multicast packets. > I don't know what it means. Do I understand correctly that there can be > only one master in the multicast domain that can send carp advertisements? > Thanks. All carp hosts send advetisements, whether they're primary or backup.
Re: iSCSI LUN mount on boot
On Fri, Feb 19, 2021 at 07:48:25PM -0500, Ashton Fagg wrote: > I'm curious as to what other folks are doing for mounting iSCSI volumes > at boot time. I've successfully configured iscsid, and mounting the > volume manually works as expected. > > I found this article [1] which suggests that hotplugd should be used. > > I also found this old presentation [2] which suggests it should "just > work" with an entry in /etc/fstab. Maybe I did not get this correct, as: > > .a /mnt/test ffs rw,noatime,nodev,nosuid,nofail 1 2 > > causes the machine to go into single-user mode on boot (presumably > because the iSCSI daemon hasn't yet started). > > Am I missing something here? Is hotplugd the preferred way to accomplish this? Yeah, the documentation is not great. You need to add 'net' to the mount options in /etc/fstab for iscsi drives. Then our rc script will do the right thing and mount these drives late (after iscsid started). .a /mnt/test ffs rw,noatime,nodev,nosuid,net 1 2 With that it should work. You can not use iscsi for /, /usr, /var but it works for /home or /var/www. -- :wq Claudio
