Re: Slow iSCSI discovery on boot halting the boot process.
On 2021-04-30 11:12, Arrigo Marchiori via freebsd-stable wrote: > On Fri, Apr 30, 2021 at 10:29:33AM +0200, Andrea Brancatelli via > freebsd-stable wrote: > >> Hello, >> >> I'm having an annoying problem with FreeBSD 12.2-RELEASE-p6, iscsid, >> geom multiparty, a Dell MD3200i and fstab. >> >> Long story short, iSCSI login/connection/whatever is slower than the >> boot process and the machine always get stuck with "cannot find >> /san_storage (/dev/multipath/...) please enter /bin/sh location" > > Did you try putting in /boot/loader.conf: > kern.cam.boot_delay=1 > > It should wait for 10 seconds before attempting to mount the root > partition. OK, I've put it in /boot/loader.conf, let's see if it helps. Unfortunately it's a production machine so I cannot reboot it now to try it. Thanks for the suggestion. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Slow iSCSI discovery on boot halting the boot process.
On 2021-04-30 10:29, Andrea Brancatelli via freebsd-stable wrote: > Hello, > > I'm having an annoying problem with FreeBSD 12.2-RELEASE-p6, iscsid, > geom multiparty, a Dell MD3200i and fstab. Geom multiparty is probably the best typo/autocorrect ever. --- Andrea Brancatelli ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Slow iSCSI discovery on boot halting the boot process.
Hello,
I'm having an annoying problem with FreeBSD 12.2-RELEASE-p6, iscsid,
geom multiparty, a Dell MD3200i and fstab.
Long story short, iSCSI login/connection/whatever is slower than the
boot process and the machine always get stuck with "cannot find
/san_storage (/dev/multipath/...) please enter /bin/sh location"
Usually we just press enter, press control-d, and the boot process
continues.
The problem is that the machine cannot boot unattended.
Those are some cfg files:
[root@arsenico ~]# cat /etc/fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/mirror/gm0s1a / ufs rw 1 1
/dev/mirror/gm0s1b none swap sw 0 0
md98 none swap sw,file=/usr/swap1,late 0 0
md99 none swap sw,file=/usr/swap0,late 0 0
/dev/mirror/gm0s1d /var ufs rw 2 2
/dev/mirror/gm0s1e /tmp ufs rw 2 2
/dev/mirror/gm0s1f /usr ufs rw 2 2
/dev/mirror/gm0s1g /repository ufs rw 2 2
fdesc /dev/fd fdescfs rw 0 0
/dev/multipath/Krypton /san_storage ufs rw,late 0 0
As you see the filesystem is already flagged as "late"...
[root@arsenico ~]# cat /etc/iscsi.conf
Krypton_C0_P0 {
TargetName=iqn.1984-05.com.dell:powervault.md3200i.6782bcb0007496a24f1e49ee
TargetAddress=10.40.3.200
}
That's the SAN, we dropped the dual connection so maybe we could get rid
of geom_multipath if that is the problem, but... hey...
[root@arsenico ~]# gmultipath list
Geom name: Krypton
Type: AUTOMATIC
Mode: Active/Active
UUID: 101b1867-c623-11e8-8bab-90e2ba021650
State: DEGRADED
Providers:
1. Name: multipath/Krypton
Mediasize: 15998753177088 (15T)
Sectorsize: 512
Mode: r1w1e1
State: DEGRADED
Consumers:
1. Name: da2
Mediasize: 15998753177600 (15T)
Sectorsize: 512
Mode: r2w2e2
State: ACTIVE
[root@arsenico ~]# camcontrol devlist
at scbus0 target 5 lun 0 (pass0,da0)
at scbus0 target 6 lun 0 (pass1,da1)
at scbus3 target 0 lun 0 (cd0,pass2)
at scbus5 target 0 lun 0 (da2,pass3)
at scbus5 target 0 lun 1f (da3,pass4)
Any interesting suggestions?
Thanks a lot.
--
Andrea Brancatelli
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: freebsd-update and speed
On 2021-04-15 14:20, Ferdinand Goldmann wrote: > I've noticed that ever since update3.freebsd.org is gone (which was in Czech > republic I think), FreeBSD updates are often quite slow for me (= > Austria/Europe) > Especially so for major release upgrades. In fact so slow that I have time > to type this mail while waiting for '8778 patches'. I was experiencing the same problem and modified freebsd-update's config file to point directly to one of the other server, can't remember if update1 or update2 and it was fast. --- Andrea Brancatelli ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Deprecating base system ftpd?
On 2021-04-05 02:05, Daniel Morante via freebsd-stable wrote: > My vote is for no. > > Reasoning is simple... at what point does it stop? By continuously moving > stuff from base to ports, FreeBSD slowly becomes just a Kernel. I strongly agree with this consideration. --- Andrea Brancatelli ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Problem with Sendmail Mailertable
Hello everybody, Disclaimer: I'm not very sure this is the best place to ask, in case feel free to point me in the right direction. Given this, I have an old 10.3 machine with sendmail 8.15.2 that's been working ok for a long time. We have a simple mailterable rule that looks like: schema31.itdbmail-lmtpd[10.33.whatever] That we use to forward mail in LMTP from sendmail to another machine where dbmail is working. Everything works as supposed but today after years of service someone realized the syntax user+mail...@schema31.it doesn't work as expected. I did a bit of research and debugging and whatever and found out that when a "+" is involved in the mail address mailertable's lookups doesn't seem to work and the mail gets sent to local mailer. I tried even something fancy like .schema31.it dbmail-lmtpd[10.33.whatever] Or even the plain all catchall . dbmail-lmtpd[10.33.whatever] But nothing works. Anybody ever stepped on this and got it working? Please, please, please, avoid the "drop sendmail and switch to " replies, if I could I would already done it ;-) Thanks a lot. -- Andrea Brancatelli ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
BSNMPD crashing
Hello everybody, I'm not very sure this is the correct place to ask, in case it's not please point me to the correct place. >From time to time my BSNMPD instance randomly crash without any apparent reason. It happens on different machines and different FreeBSD releases. It happened tonight as well on one of our servers. Usually I just delete the bsnpmd.core file and restart the service, but I thought there may be someone interested in looking at the core to understand what the reason may be? The bsnmpd daemon is in a private network so malicious stuff is not the case, and is used by a central Cacti instance to do usual graphs to monitor cpus, disks, memory, lan cards and whatever. The servers usually have high uptimes and quite solid network traffic. The core file is 1.3GB with seems pretty a lot to me, so maybe it died because it's leaking memory? If anyone is interested please feel free to contact me otherwise I'll just delete it :-) -- Andrea Brancatelli ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: chsh corrupts /etc/pwd.db
On 2019-08-22 12:43, Miroslav Lachman wrote: >> I run in to something similar from time to time from about 10.x or 8.x (i >> skipped 9.x) >> I do not remember exactly what command did the corruption, if it was vipw or >> chsh or something else to manipulate user database. The fix was easy - run >> it again or use pwd_mkdb > > I searched our archive of issues and found it. It was error with "pw" command > which sometimes failed in very weird way: > > # pw useradd -n user1 -u 1003 -G wheel -s /bin/tcsh -m -M 0700 -c "User One" > > pw: user 'user1' disappeared during update > > It was on FreeBSD 8.x. So it is different error than yours. It still happens nowadays when you upgrade from FreeBSD 10.x to 11.x or from 11.x to 12.x. It doesn't happens deterministically but after upgrading the machines I often find myself with PKG unable to upgrade some programs because it cannot delete/add users. The fix is, as already said, pwd_mkdb (-p) --- Andrea Brancatelli ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
