suggestion for protection netconfig_ipv4 from empty fields
Hi In bsdinstaller on netconfig_ipv4 stage possible situation of record with empty values ifconfig in rc.conf. For this purpose it is necessary on a question "Would you like to configure IPv4 for this interface" choose "Yes", then "No" for configuring via DHCP and in the dialog forms with IP Address, Subnet Mask and GW choose "Ok" without any data. After this rc.conf will contain: ifconfig_IF=" inet netmask " that isn't critical but generates "ifconfig: 'netmask' requires argument" warning when netif service start. I suggest to add similar to this: == --- /usr/libexec/bsdinstall/netconfig_ipv4 2011-11-03 23:47:15.920391101 +0400 +++ /netconfig_ipv4 2011-11-04 01:59:49.573390155 +0400 @@ -69,6 +69,12 @@ 'Default Router' 3 0 "$ROUTER" 3 20 16 0 \ 2>&1 1>&3) if [ $? -eq $DIALOG_CANCEL ]; then exit 1; fi + +if [ `echo $IF_CONFIG| tr ' ' '\n' |grep -c .` -ne 3 ]; then + dialog --backtitle "FreeBSD Installer" --title "Error" --msgbox \ + "All fields should be filled" 0 0 + exit 1 +fi exec 3>&- echo $INTERFACE $IF_CONFIG | == Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: problem with whereis rar and portinstall on the fresh installation of FreeBSD 9.0-RC1
On Sat, Oct 22, 2011 at 1:51 PM, George Kontostanos
wrote:
> On Fri, Oct 21, 2011 at 12:28 PM, Subbsd wrote:
>>
> I had the same problem. It was solved by recompiling rubby1-8, and
> performing a portsnap fetch extract again.
>
I have found that this behavior arises if to remove portupgrade
checkbox by default
"BDB4 Use Berkeley DB> = 2 as backend"
When I returned back to this dependency (installed ruby {18,19}-bdb)
- the upgrade process was successful
It turns out that this option is obligatory and it shouldn't be removed. Thanks.
>
> --
> George Kontostanos
> aisecure.net
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 9.0-RC1 freeze after swapoff/swapon procedure on md/vnode-backend file
Hi I get easy reproducible a hang-up servers that use the file-based swap file after swapoff / swapon procedure (in this case, some of the data must be swapped). For example: 1) dd if=/dev/zero of=/usr/swp1 bs=1m count=100 2) mdconfig -a -t vnode -f /usr/swp1 3) swapon /dev/md0 4) begin to allocated memory, for example by simple: tail /dev/zero 5) after a filling of some percent, do swapoff /dev/md0, then swapon /dev/md0. you can try this procedure again. The system may stop responding to commands and freezes or locks up after some time. From the outside - the core lives (icmp response goes) but the disk system is not available. PS: one of my server to my mind is frozen without swapoff/on - just had three swapfile, a day after he crashed. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
VFS problem with ?fcntl SETLK? and nullfs
Hi
I found a bad issue in FreeBSD mounts nullfs file system, which may
appear in the random.
Initially, I get problems on FreeBSD-current on the host that have a
large number JAIL at the time when they start. Handbook scenario:
1) have readonly base (for example /usr/jails/base)
2) have write area for jail personal data (for example:
/usr/jails/j1data/{home,var,local,...})
3) mount RO base to new jail location, then mount RW part data above RO
In some cases, i watched the freeze of the system when working nullfs
mount, but could not find a reason.
On a test environment I have tried to simulate mount_nullfs with
different types of actions by the source directory:
- through dd(1) to make an huge oveload by read - does not affect
- through dd(1) to make an huge overload by write - does not affect
- through script to delete, create random-files in large numbers -
does not affect
but now I can easily with a 100% guarantee show the problem - it is
easily obtained by working with "svn cleanup" action.
For example on the directory /usr/src obtained from SVN. If start in /usr/src
svn cleanup
and at the same time try to mount_nullfs the problem appears.
As far as I can see, cleanup makes frequent lock files. It seems to
me, who some of the lock is simply not true and is inherited by a
deadlock.
I wrote sample scripts simulating the problem. I did a rotation
mount-ro + mount-rw specifically - is the repetition of the way
described in the handbook section of jail.
Since the problem can appear in random moment, I made an infinite
loop. But I am getting the problem is usually the first-pass. Here is
it:
---/cut/-
#!/bin/sh
SRCROOT="/usr/src"
DSTROOT="/usr/nullfstest"
ITER=`seq 100`
MOUNTO=`find ${SRCROOT} -type d -maxdepth 1 -exec basename {} \;`
[ -d "${DSTROOT}" ] || mkdir $DSTROOT
mount_subdir()
{
for mto in ${MOUNTO}; do
if [ -d "${1}/$mto" ]; then
mount -orw -t nullfs /bin ${1}/${mto}
fi
done
}
cd ${SRCROOT}
while [ 1 ]; do
echo "Mount phase"
lockf -s -t0 /tmp/svn.lock svn cleanup &
for iter in $ITER; do
DST="${DSTROOT}/${iter}"
[ -d "${DST}" ] || mkdir ${DST}
mount -oro -t nullfs ${SRCROOT} ${DST}
mount_subdir ${DST}
done
echo "Unmount phase"
mount -t nullfs |awk {'printf "umount -f "$3"\n"'} |sh
done
---/end of cut/-
Last syscall I can see this svn cleanup is:
fcntl(3,F_SETLK,0x7fffc9b0)
where 3 - fd of some \.svn/file.
looks like in action this way - the system (kernel) works. but if the
process or your session will affect an action in the source directory
(in this example - /usr/src), for example:
cd /usr/src
fstat /usr/src/*
ls /usr/src/
- Get filesystem deadlock. In addition, the system in this state does
not reboot without help - system do not return from free buffer to
storage stage.
in FreeBSD 9.0 RC1 bug exists.
PS: An important detail - I could not get the problem on FreeBSD
running under a virtual machine (VirtualBox) - maybe due to the tick /
hz.kern issue?
PS2: what file system - does not matter. I get the problem on ZFS as
well as for UFS
Please check this informatio. it seems that this is serious
Thanks.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
problem with whereis rar and portinstall on the fresh installation of FreeBSD 9.0-RC1
Hi, I see the problems that have never been observed: a) portinstall -c editors/hexedit [database version mismatch/bump detected] [Updating the portsdb in /usr/ports ... - 22822 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000 HASH: Out of overflow pages. Increase page size error] Remove and try again. [Updating the portsdb in /usr/ports ... - 22822 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000 HASH: Out of overflow pages. Increase page size error] Remove and try again. [Updating the portsdb in /usr/ports ... - 22822 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000 HASH: Out of overflow pages. Increase page size error] Remove and try again. [Updating the portsdb in /usr/ports ... - 22822 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000 HASH: Out of overflow pages. Increase page size error] Remove and try again. [Updating the portsdb in /usr/ports ... - 22822 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000 HASH: Out of overflow pages. Increase page size error] Remove and try again. [Updating the portsdb in /usr/ports ... - 22822 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000 HASH: Out of overflow pages. Increase page size error] Remove and try again. [Updating the portsdb in /usr/ports ... - 22822 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000.15000.16000.17000.18000.19000.2.21000.22000 HASH: Out of overflow pages. Increase page size error] Remove and try again. [Updating the portsdb in /usr/ports ... - 22822 port entries found .1000.2000.3000.4000.5000.6000...^C (infninity loop?) b) whereis rar - hang up until you do not press Ctrl + D, output in this case: rar: /usr/local/bin/rar /usr/local/man/cat1/rar.1 (source: ) /usr/ports/archivers/rar System: Fresh install FreeBSD 9.0-amd64. Before on 9.0beta3 is everything was fine. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
watchdog timeout for pwait/rc.shutdown
Hi Tell me please, is it possible to change the behavior of shutdown sequence to avoid work of kill process (or increase timeout). Тot always process can not react to signals and stop - for example, heavy MySQL server databases or databases/redis - can not keep up with 30 seconds to correct shutdown. In my example noSQL product - redis holds a 10 GB RAM memory and when stop it just did not have time to reset the state to disk when i stop process or jail with redis. As result ive have in /var/db/redis "dump.tmp.XX" - broken DB about ~3 Gb instead of 10 GB. Waiting for PIDS: 47924 30 second watchdog timeout expired. Shutdown terminated. Thu Jul 14 16:24:30 MSD 2011 Killed PS: I may be mistaken but I think this problem did not exist before PS2: i have RELENG_8 and HEAD version of FreeBSD PS3: Thanks in advance ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Webcamd testers wanted on FreeBSD 8.2
On Sat, Jan 8, 2011 at 10:46 PM, kerbzo wrote: > I use one webcam with webcamd but sometime after reboot /dev/video0 is > not created at all. BTW, it may be associated with the initialization of the USB ports - this situation reminded me of the problem with external USB devices (cdrom or usb memstick) in sysinstall FreeBSD 8x - in some case the device was not found without the "Re-Scan Devices". Sometimes it is not required and it is not required on FreeBSD 7x. Re-Scan - it's just power reset as I understand ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Webcamd testers wanted on FreeBSD 8.2
On Sat, Jan 8, 2011 at 8:41 PM, Hans Petter Selasky wrote: > > Hi, > > Can someone running FreeBSD 8.2-RC1 with more than one or external USB webcam > or DVB-XXX devices verify the following: > > Hello. Can the boot sequence of .ko modules in loader.conf somehow influence the success of the detection camera? I've seen this problem on FreeBSD-current amd64 some time ago. Maybe it was a coincidence - but the /dev/video0 does not always appear when loading the module was at the end of the list. In the near future I will test in 9-0 CURRENT and 8.2-RC2 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 7.2-RC boot problem
On Monday 27 April 2009 21:31:38 Jim Pingle wrote: > subbsd wrote: > > Hello, i've got some problem with my SATA Optiarc DVD RW: > > message output on the screen in not stopped, but repeating with > > incremental delay: > > ... > > acd0: DVDR at ata3-master UDMA33 > > HEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install > Hi. > Did you retype this? Or did it really say "HEOM"? If that's not a typo, > you may want to check for RAM errors. > Correct. RAM is ok, problem in my fingers ;). > > run_interrupt_driven hooks: still waiting after 60 seconds for xpt_config > > run_interrupt_driven hooks: still waiting after 120 seconds for > > xpt_config run_interrupt_driven hooks: still waiting after 180 seconds > > for xpt_config run_interrupt_driven hooks: still waiting after 240 > > seconds for xpt_config run_interrupt_driven hooks: still waiting after > > 300 seconds for xpt_config > > I spoke with someone the other day who had that exact same message, and > it was due to either a Firewire controller in the BIOS, or a USB card > reader. They disabled both at the same time, and the message went away. > Yes, really when IE1394 is disabled in bios problem is gone. Thanks! May be this info make sense for publish in RelNotes? > That appears to be the CAM subsystem probing for root-capable devices, > from what I found via Google the other day. > > Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 7.2-RC boot problem
On Monday 27 April 2009 19:05:16 Ken Smith wrote: > On Mon, 2009-04-27 at 11:03 -0300, Paulo Fragoso wrote: > > I can't boot on cdrom sata, this problem doesn't exist in older releases. > > > > My motherboard is > > Gigabyte GA-M61PME-S2 > > > > On FreeBSD 7.1 my cdrom drive is detected this way: > > acd0: DVDR at ata3-master SATA150 > > Just checking - is *everything* the same? For example is the media the > same? Depending on a variety of things I've had issues with rewritable > media versus write-once media, etc. > > The machine I test the release builds on before uploading them has a > Gigabyte motherboard (G31M-ES2L) with a sata drive in it so it's not a > generic "sata doesn't work" issue: > > acd0: DVDROM at ata0-slave SATA150 > > If none of that helps we'd need more information about how far it gets > before it stops. Hello, i've got some problem with my SATA Optiarc DVD RW: message output on the screen in not stopped, but repeating with incremental delay: ... acd0: DVDR at ata3-master UDMA33 HEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install run_interrupt_driven hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven hooks: still waiting after 240 seconds for xpt_config run_interrupt_driven hooks: still waiting after 300 seconds for xpt_config ... .. Motherboard is Asus m3n78-em. I've check CD - FreeBSD 7.1-RELEASE disc1 for amd64 - FreeBSD 7.2-RC2 disc1 for amd64 - PCBSD 7.1 DVD for i386 With equally results ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 7.2-BETA1 Available
Hello maillist. Can somewhere see release notes for 7.2 now? Thanks! > At 12:43 AM 4/3/2009, Ken Smith wrote: > >The first of the test builds for the FreeBSD 7.2-RELEASE cycle is now > >available. Testing of two recent changes to the system would be ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
