lprof startup issue, QAssistantClient not found
After installing (and reinstalling) devel/lprof, I keep getting the error: "The QAssistantClient executable was not found. Make sure that assistant(.exe)is located either in your PATH or in the $QTDIR/bin directory. Help will not be availble until this is corrected." I have both devel/qt4-assistant devel/qt4-assistant-adp installed, but that doesn't seem to make any difference. "assistant-qt4" and "assistant_adp" both exist in /usr/local/bin If I create a symbolic link of "assistant" to either of the assistant* executables I no longer get the error message, but no help shows up either... ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Network startup with age Ethernet device
Thank you, that's what I needed. Best regards, Olivier On Wed, Sep 4, 2013 at 11:04 PM, Michael Sierchio wrote: > On Wed, Sep 4, 2013 at 8:49 AM, Lowell Gilbert < > freebsd-questions-lo...@be-well.ilk.org> wrote: > >> >> Have you tried using netwait? >> I think that would involve putting enable_netwait in rc.conf, and >> > > netwait_enable="YES" would be it. > > - M > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Network startup with age Ethernet device
On Wed, Sep 4, 2013 at 8:49 AM, Lowell Gilbert < freebsd-questions-lo...@be-well.ilk.org> wrote: > > Have you tried using netwait? > I think that would involve putting enable_netwait in rc.conf, and > netwait_enable="YES" would be it. - M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Network startup with age Ethernet device
Olivier Nicole writes: > I want to set-up a small server from an Asus P5L-MX motherboard. > > It has an onboard gigabit Ethrnet that works with the driver age. > > Problem is that at boot, I experience the interface to go up and down a > couple of times, and it is usually down when Apache try to start, so > Apache would not start (nor ntpd). > > I resolved to add a 5 seconds sleep in /etc/rc.d/netif but there may be > a more elegant way to solve that. Have you tried using netwait? I think that would involve putting enable_netwait in rc.conf, and configuring an address for it to check; probably the gateway would be good enough. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Network startup with age Ethernet device
Hi, I want to set-up a small server from an Asus P5L-MX motherboard. It has an onboard gigabit Ethrnet that works with the driver age. Problem is that at boot, I experience the interface to go up and down a couple of times, and it is usually down when Apache try to start, so Apache would not start (nor ntpd). I resolved to add a 5 seconds sleep in /etc/rc.d/netif but there may be a more elegant way to solve that. Help is welcome. Thanks in advance, Olivier In the extract of /var/log/message below you can see 6 seconds delay between the ifconfig and the interface finally up and running. By that time ntpd and apache have failed starting. Sep 4 16:36:58 door kernel: Starting Network: lo0 age0 plip0. Sep 4 16:36:58 door kernel: lo0: flags=8049 met\ ric 0 mtu 16384 Sep 4 16:36:58 door kernel: options=63 Sep 4 16:36:58 door kernel: inet6 ::1 prefixlen 128 Sep 4 16:36:58 door kernel: inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 Sep 4 16:36:58 door kernel: inet 127.0.0.1 netmask 0xff00 Sep 4 16:36:58 door kernel: nd6 options=21 Sep 4 16:36:58 door kernel: age0: flags=8843 metric 0 mtu 1500 Sep 4 16:36:58 door kernel: options=c319b [...] Sep 4 16:37:00 door kernel: age0: link state changed to UP Sep 4 16:37:00 door kernel: age0: link state changed to UP Sep 4 16:37:01 door kernel: age0: link state changed to DOWN Sep 4 16:37:01 door kernel: age0: link state changed to DOWN [...] Sep 4 16:37:04 door kernel: age0: link state changed to UP Sep 4 16:37:04 door kernel: age0: link state changed to UP -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Finding exactly which commands, and in which order, rc is running at startup
Thanks for all the suggestions. Of them, this was the one that helped me with my issue: On Aug 23, 2013, at 1:41 AM, Doug Hardie wrote: > You can add: > > rc_debug="YES" > > to /etc/rc.conf and that might give you what you need. According to the man > page it will "produces copious output to the terminal and syslog(3)" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Finding exactly which commands, and in which order, rc is running at startup
On 23 August 2013 10:41, Doug Hardie wrote: > > On 22 August 2013, at 13:07, Paul Hoffman wrote: > > > Greetings again. After doing a freebsd-update, my system is starting up > differently than it was before. I want to figure out why before I come here > and say "it's broken". > > > > Is there a way to say "show me all of the commands you are running > during startup"? It would be grand if I could say "tell me what you would > do next time (dry run)", but "what did you do last time" is OK too. > > You can add: > > rc_debug="YES" > > to /etc/rc.conf and that might give you what you need. According to the > man page it will "produces copious output to the terminal and syslog(3)" > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > You can use "rcorder /etc/rc.d/* /usr/local/etc/rc.d/*" to show the order of which the startup scripts is run. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Finding exactly which commands, and in which order, rc is running at startup
On 22 August 2013, at 13:07, Paul Hoffman wrote: > Greetings again. After doing a freebsd-update, my system is starting up > differently than it was before. I want to figure out why before I come here > and say "it's broken". > > Is there a way to say "show me all of the commands you are running during > startup"? It would be grand if I could say "tell me what you would do next > time (dry run)", but "what did you do last time" is OK too. You can add: rc_debug="YES" to /etc/rc.conf and that might give you what you need. According to the man page it will "produces copious output to the terminal and syslog(3)" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Finding exactly which commands, and in which order, rc is running at startup
On 22/08/2013 21:07, Paul Hoffman wrote: > Greetings again. After doing a freebsd-update, my system is starting > up differently than it was before. I want to figure out why before I > come here and say "it's broken". > > Is there a way to say "show me all of the commands you are running > during startup"? It would be grand if I could say "tell me what you > would do next time (dry run)", but "what did you do last time" is OK > too. How much detail do you want? You probably can't get a report on every single process run during the boot process at all easily. However, you can see the console output from the boot process. To see what the kernel emits on boot-up, look at /var/run/dmesg.boot -- if you've got an old copy of dmesg.boot around somewhere, comparing the two should show you any changes in the devices the kernel discovers when it probes your system. To see the output from the rc system, the best thing is to enable the console log. Edit /etc/syslog.conf and uncomment the indicated line, as so: # uncomment this to log all writes to /dev/console to /var/log/console.log console.info/var/log/console.log Then do: touch /var/log/console.log chmod 600 /var/log/console.log /etc/rc.d/syslogd restart Obviously, that won't help you see what happened on the previous reboot, but on the next reboot you should see a transcript of the console output. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Finding exactly which commands, and in which order, rc is running at startup
Greetings again. After doing a freebsd-update, my system is starting up differently than it was before. I want to figure out why before I come here and say "it's broken". Is there a way to say "show me all of the commands you are running during startup"? It would be grand if I could say "tell me what you would do next time (dry run)", but "what did you do last time" is OK too. --Paul Hoffman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: any way to stop boot2 from waiting for keypress at system startup
Yes you are right :) If i knew the feature's name, it would be easier to find this option out.. Actually i found mentioned flag while tracing boot2.c code... Anyway, Thank you for your complete reply :) On Wed, Jul 3, 2013 at 6:35 AM, Polytropon wrote: > On Tue, 2 Jul 2013 15:18:04 +0430, takCoder wrote: > > i found the answer! if i add a "-n" parameter to /boot.config file, the > > mentioned feature will be disabled.. > > Sorry for my confusion. The option you've successfully found > is documented in "man 8 boot" (which also provides a short > description of the stages performed at system boot). That's > why it's good to know how the different components of the > boot process are named so it becomes more logical where to > search. :-) > > From the manual page: > > -nignore key press to interrupt boot before loader(8) > is invoked. > > Explained: > > However, it is possible to dispense with the third stage altogether, > either by specifying a kernel name in the boot block parameter file, > /boot.config, or, unless option -n is set, by hitting a key during a > brief pause (while one of the characters -, \, |, or / is displayed) > before loader(8) is invoked. Booting will also be attempted at stage > two, if the third stage cannot be loaded. > > It's always good to know where thine documentation is. ;-) > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: any way to stop boot2 from waiting for keypress at system startup
On Tue, 2 Jul 2013 15:18:04 +0430, takCoder wrote: > i found the answer! if i add a "-n" parameter to /boot.config file, the > mentioned feature will be disabled.. Sorry for my confusion. The option you've successfully found is documented in "man 8 boot" (which also provides a short description of the stages performed at system boot). That's why it's good to know how the different components of the boot process are named so it becomes more logical where to search. :-) >From the manual page: -nignore key press to interrupt boot before loader(8) is invoked. Explained: However, it is possible to dispense with the third stage altogether, either by specifying a kernel name in the boot block parameter file, /boot.config, or, unless option -n is set, by hitting a key during a brief pause (while one of the characters -, \, |, or / is displayed) before loader(8) is invoked. Booting will also be attempted at stage two, if the third stage cannot be loaded. It's always good to know where thine documentation is. ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: any way to stop boot2 from waiting for keypress at system startup
i found the answer! if i add a "-n" parameter to /boot.config file, the mentioned feature will be disabled.. On Tue, Jul 2, 2013 at 11:16 AM, takCoder wrote: > Thank you for your quick reply. :) > > Unfortunately, no.. the option you are talking about is for limitting or > disabling beastie menu waiting time, and i am using the option you mention > as well.. > > I wait to disable a feature one step before that.. before even loading > kernel.. i just don't know what exactly its name is.. but it's just at the > beginning of boot2 procedure; it waits for 3 seconds for user input and if > you press any key, it shows you the prompt i mentioned and so on.. > if there is no key-press, the normal process will go on.. > > Best Regards, > t.a.k > > > On Tue, Jul 2, 2013 at 11:10 AM, Polytropon wrote: > >> On Tue, 2 Jul 2013 11:05:22 +0430, takCoder wrote: >> > Hi Everyone, >> > >> > i wanna stop boot2 from getting a input string to change default boot >> > point.. is there any way around, other than changing boot2.c source >> code to >> > disable this feature?? >> > >> > As you may know, on system-startup, if you press any key, you will see >> the >> > following prompt, waiting for you to enter related string: >> > FreeBSD/x86 boot >> > Default: 0:ad(0,a) >> > boot: >> > >> > I checked it and found out that i can change boot2.c file to disable >> this >> > section.. but I'd rather find another way.. Would you please let me know >> > whether there are any other ways to do so? >> >> Without having checked it, but is this what you are searching for? >> >> In /boot/loader.conf: >> >> autoboot_delay="-1" >> >> From /boot/defaults/loader.conf: >> >> Delay in seconds before autobooting, >> set to -1 if you don't want user to be >> allowed to interrupt autoboot process and >> escape to the loader prompt, set to >> "NO" to disable autobooting >> >> I'm using autoboot_delay="1" to limit the time which the system >> is waiting before continuing the boot process. >> >> >> >> -- >> Polytropon >> Magdeburg, Germany >> Happy FreeBSD user since 4.0 >> Andra moi ennepe, Mousa, ... >> > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: any way to stop boot2 from waiting for keypress at system startup
Thank you for your quick reply. :) Unfortunately, no.. the option you are talking about is for limitting or disabling beastie menu waiting time, and i am using the option you mention as well.. I wait to disable a feature one step before that.. before even loading kernel.. i just don't know what exactly its name is.. but it's just at the beginning of boot2 procedure; it waits for 3 seconds for user input and if you press any key, it shows you the prompt i mentioned and so on.. if there is no key-press, the normal process will go on.. Best Regards, t.a.k On Tue, Jul 2, 2013 at 11:10 AM, Polytropon wrote: > On Tue, 2 Jul 2013 11:05:22 +0430, takCoder wrote: > > Hi Everyone, > > > > i wanna stop boot2 from getting a input string to change default boot > > point.. is there any way around, other than changing boot2.c source code > to > > disable this feature?? > > > > As you may know, on system-startup, if you press any key, you will see > the > > following prompt, waiting for you to enter related string: > > FreeBSD/x86 boot > > Default: 0:ad(0,a) > > boot: > > > > I checked it and found out that i can change boot2.c file to disable this > > section.. but I'd rather find another way.. Would you please let me know > > whether there are any other ways to do so? > > Without having checked it, but is this what you are searching for? > > In /boot/loader.conf: > > autoboot_delay="-1" > > From /boot/defaults/loader.conf: > > Delay in seconds before autobooting, > set to -1 if you don't want user to be > allowed to interrupt autoboot process and > escape to the loader prompt, set to > "NO" to disable autobooting > > I'm using autoboot_delay="1" to limit the time which the system > is waiting before continuing the boot process. > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: any way to stop boot2 from waiting for keypress at system startup
On Tue, 2 Jul 2013 11:05:22 +0430, takCoder wrote: > Hi Everyone, > > i wanna stop boot2 from getting a input string to change default boot > point.. is there any way around, other than changing boot2.c source code to > disable this feature?? > > As you may know, on system-startup, if you press any key, you will see the > following prompt, waiting for you to enter related string: > FreeBSD/x86 boot > Default: 0:ad(0,a) > boot: > > I checked it and found out that i can change boot2.c file to disable this > section.. but I'd rather find another way.. Would you please let me know > whether there are any other ways to do so? Without having checked it, but is this what you are searching for? In /boot/loader.conf: autoboot_delay="-1" >From /boot/defaults/loader.conf: Delay in seconds before autobooting, set to -1 if you don't want user to be allowed to interrupt autoboot process and escape to the loader prompt, set to "NO" to disable autobooting I'm using autoboot_delay="1" to limit the time which the system is waiting before continuing the boot process. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
any way to stop boot2 from waiting for keypress at system startup
Hi Everyone, i wanna stop boot2 from getting a input string to change default boot point.. is there any way around, other than changing boot2.c source code to disable this feature?? As you may know, on system-startup, if you press any key, you will see the following prompt, waiting for you to enter related string: FreeBSD/x86 boot Default: 0:ad(0,a) boot: I checked it and found out that i can change boot2.c file to disable this section.. but I'd rather find another way.. Would you please let me know whether there are any other ways to do so? Thank you all in advance :) Best Regards, takCoder ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
already active DMA on this device FAILURE at startup
hello all, i have FreeBSD8.2 on my system. occasionally, i see some strange errors in startup and freebsd can not boot correctly. when i reset my system everything is ok and freebsd boot successfully. these are errors which appear in statrtup: ata1: setting up DMA failed ad3: WARNING - READ_DMA requeued due to channel reset LBA=25167888 ata1: FAILURE - already active DMA on this device these errors repeat more and more. i don't know what's wrong in my freebsd. i have used freebsd for several years and have not seen these errors before. last few days ago, i set a separate partition for etc. can separate etc partition cause this problem? how can i solve it to never see these errors again? (i need a separate partition for etc) thanks in advance, SAM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
9.1-release bridge config at startup not working
Hello list After pretty much of googling I was able to make this bridge setup up and running: cloned_interfaces="bridge0" ifconfig_bridge0="addm igb6 addm igb7" ifconfig_bridge0_alias0="inet x.x.x.x netmask x.x.x.x" ifconfig_igb6="up" ifconfig_igb7="up" however I'm running xorp pim multicast router on the box as well and it complains about not being able to get the primary IP address of bridge0. And I need xorp running on that subnet. (after manually assigning an IP to bridge0, bridge0 becomes unresponsive) I tried autobridge according to some sparse "documentation" found, but autobridge with setup: cloned_interfaces="bridge0" autobridge_interfaces="bridge0" autobridge_bridge0="igb6 igb7" ifconfig_bridge0="inet x.x.x.x netmask x.x.x.x" ifconfig_igb6="up" ifconfig_igb7="up" does not start at all. I end up with having only igb6 added in bridge0 without an IP address. Well, I would gladly live without a bridge ;) if somebody could give me a hit how to protect a group of servers on the same subnet as the router is. Without a need of NAT or IP changes. I need a DMZ, so I thought I'd simply put the boxes behind a filtered bridge. Seems like it's not that easy as it sound. Thank you very much for any kind of help/advice Peter Huncar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Startup Notification?
Walter Hurry gmail.com> writes: > > I'm running FreeBSD 9.1RC3 with LXDE and OpenBox. > > The startup-notification port is installed (it's required by a number of > other ports anyway), but I don't actually see any form of visual > notification when opening GUI applications. For many of these (e.g. > lxterminal, pcmanfm) this doesn't matter, since they appear virtually > instantaneously, but for others (like firefox) the lack is something of a > nuisance. > > Am I missing an optional port, or is there a configuration file somewhere > which I need to edit? This narrative should give you some clue: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/11462 Find a file like e.g. mozilla-firefox.desktop that will look similar to this: ... Exec=firefox %u Icon=firefox Terminal=false Type=Application StartupWMClass=Firefox-bin MimeType=text/html;text/xml;application/xhtml+xml;application /vnd.mozilla.xul+xml;text/mml; StartupNotify=true X-Desktop-File-Install-Version=0.15 Categories=Network;WebBrowser; jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Startup Notification?
I'm running FreeBSD 9.1RC3 with LXDE and OpenBox. The startup-notification port is installed (it's required by a number of other ports anyway), but I don't actually see any form of visual notification when opening GUI applications. For many of these (e.g. lxterminal, pcmanfm) this doesn't matter, since they appear virtually instantaneously, but for others (like firefox) the lack is something of a nuisance. Am I missing an optional port, or is there a configuration file somewhere which I need to edit? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mysqld startup issue
On 06/11/12 13:48, Robert Bonomi wrote: >> Unfortunately, mysqld won't start: >> > [ sneck ] > >> 120611 10:55:52 [ERROR] Can't open the mysql.plugin table. Please run >> mysql_upgrade to create it. > Have you tried doing what the error message _tells_ you to do ? nope, and yup nope, because the docs clearly state that the server needs to be running. yup, because I did it anyway just to see what it would do > If so, what happened? Unsurprisingly, it craps out saying it cannot connect to the server. problem was missing --datadir option when starting server ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
[solved] Re: mysqld startup issue
Ugh. Operator error. I assumed from the docs there had to be a my.cnf file someplace, if only to serve as the system default; and that the my.cnf file was directing everything else. It turns out there doesn't have to be one anywhere. My thought process was hijacked by the errors produced from the missing --datadir option starting using: mysqld --datadir= was all that was required, although clearly a my.cnf or ~/.my.cnf would make things easier. > 120611 10:55:52 [Warning] Can't create test file > /var/db/mysql/breakaway.lower-test > mysqld: Table 'mysql.plugin' doesn't exist > 120611 10:55:52 [ERROR] Can't open the mysql.plugin table. Please run > mysql_upgrade to create it. > 120611 10:55:52 InnoDB: The InnoDB memory heap is disabled > 120611 10:55:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins > 120611 10:55:52 InnoDB: Compressed tables use zlib 1.2.5 > 120611 10:55:52 InnoDB: Initializing buffer pool, size = 128.0M > 120611 10:55:52 InnoDB: Completed initialization of buffer pool > 120611 10:55:52 InnoDB: Operating system error number 13 in a file operation. > InnoDB: The error means mysqld does not have the access rights to > InnoDB: the directory. > InnoDB: File name ./ibdata1 > InnoDB: File operation call: 'create'. > InnoDB: Cannot continue operation. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mysqld startup issue
Gary Aitken wrote: > To: FreeBSD Mailing List > Subject: mysqld startup issue > > I've done the following after having a running system with a running mysql on > it: > > moved user accounts, although no logical move: > /usr/home/foo was => /hd1/foo > now > /usr/home => /hd1/home and /hd1/foo is now /hd1/home/foo > repartitioned the SSD and restored the system from a dump taken prior to > repartitioning. > removed all ports and reinstalled them > > Unfortunately, mysqld won't start: > [ sneck ] > 120611 10:55:52 [ERROR] Can't open the mysql.plugin table. Please run > mysql_upgrade to create it. [ sneck ] > > This looks like some kind of access / setuid problem, but I'm not sure what. > Suggestions? Have you tried doing what the error message _tells_ you to do ? If so, what happened? If not, why not? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mysqld startup issue
Gary Aitken wrote: > I've done the following after having a running system with a running mysql > on it: > > moved user accounts, although no logical move: > /usr/home/foo was => /hd1/foo > now > /usr/home => /hd1/home and /hd1/foo is now /hd1/home/foo > repartitioned the SSD and restored the system from a dump taken prior to > repartitioning. removed all ports and reinstalled them Although I have not really experienced much in the way of toruble with this, as my systems are not very 'busy', it can be better to boot from a LiveCD to do the dump because no files are open for writing and all your MySQL files will be static. No possibility of change during the dump. That being said, I have done dumps from live filesystems and have been able to restore them many times. Forewarned is forearmed. > Unfortunately, mysqld won't start: > > 120611 10:55:52 [Warning] Can't create test file > /var/db/mysql/breakaway.lower-test 120611 10:55:52 [Warning] Can't create > test file /var/db/mysql/breakaway.lower-test mysqld: Table 'mysql.plugin' > doesn't exist 120611 10:55:52 [ERROR] Can't open the mysql.plugin table. > Please run mysql_upgrade to create it. 120611 10:55:52 InnoDB: The InnoDB > memory heap is disabled 120611 10:55:52 InnoDB: Mutexes and rw_locks use > GCC atomic builtins 120611 10:55:52 InnoDB: Compressed tables use zlib > 1.2.5 120611 10:55:52 InnoDB: Initializing buffer pool, size = 128.0M > 120611 10:55:52 InnoDB: Completed initialization of buffer pool > 120611 10:55:52 InnoDB: Operating system error number 13 in a file > operation. InnoDB: The error means mysqld does not have the access rights > to InnoDB: the directory. > InnoDB: File name ./ibdata1 > InnoDB: File operation call: 'create'. > InnoDB: Cannot continue operation. I have had trouble before when playing with these files outside of MySQL. What happens is if they get out of sync with the index they will become totally unusable. There are recovery procedures in the docs, but if memory serves it was just easier to delete the ib_logfile(x) and allow MySQL to recreate from scratch. Probably not central to your problem, per se, just thought I'd make mention in passing. I would recommend consulting the docs on this subject of index/logfile recovery prior to any blindly mucking about. > Running mysqld --verbose shows: > > basedir /usr/local > general-log-file/var/db/mysql/breakaway.log Usually this file is of the form .err > ls -aol /usr/local/libexec/mysqld > -rwxr-xr-x 1 root wheel - 9558944 Jun 11 10:40 mine shows: testbed# ls -aol /usr/local/libexec/mysqld -r-xr-xr-x 1 root wheel - 6694672 May 10 11:16 /usr/local/libexec/mysqld > /usr/local/libexec/mysqld ls -dl /var/db/mysql > drwxr-xr-x 2 mysql mysql 512 Jun 11 10:31 /var/db/mysql and my /var/db shows the below for the mysql directory: drwxr-xr-x 21 mysql mysql3072 Jun 4 12:09 mysql > cd / > find . -ls | grep my.cnf > > shows nothing. > > This looks like some kind of access / setuid problem, but I'm not sure > what. Suggestions? Beginning with the mysql_enable="YES" I have found when using rc startup scripts you need the entire path: /usr/local/etc/rc.d/mysql-server Moving on to permissions. Don't recall specifically, but if memory serves during the port install/reinstall there is a choice displayed to keep/use a previous mysql:mysql user and group combo. Perhaps an incorrect choice allows for deleting this - never known as I have always chosen to not delete but to reuse the old accounts. Nevertheless, in /etc/group there should be an entry like this: mysql:*:88: And the user account as shown by vipw will look like this: mysql:*:88:88::0:0:MySQL Daemon:/nonexistent:/sbin/nologin These should both be handled 'automagically' by the ports build system. You can cd to /var/db and do a chown -R mysql:mysql mysql if you want to ensure file ownership is correct, provided the above referenced entries are in place. The ports these days will place the my.cnf file in /usr/local/etc instead of the old location of /var/db/mysql. I believe it is still supposed to fall back to /var/db/mysql if not found. One thing I found out when I was having a problem was that MySQL will not source this file if permissions on it are world read/write. Not exactly sure what it's supposed to be (I'm sure this can be found in the docs) but I've just chmod'd it 444 when I'm done with edits. I do not grasp why any movement of your home directories mentioned at the top would matter to MySQL. I suspect something more to do with the "removed all ports and reinstalled them" part. The mysql.plugin tells you to run an update script to update schema. There is more info o
Re: mysqld startup issue
On 11-Jun-2012, at 11:02 PM, Gary Aitken wrote: > I've done the following after having a running system with a running mysql on > it: > > moved user accounts, although no logical move: > /usr/home/foo was => /hd1/foo > now > /usr/home => /hd1/home and /hd1/foo is now /hd1/home/foo > repartitioned the SSD and restored the system from a dump taken prior to > repartitioning. > removed all ports and reinstalled them > > Unfortunately, mysqld won't start: > > 120611 10:55:52 [Warning] Can't create test file > /var/db/mysql/breakaway.lower-test What's the permission of /var/db/mysql? Also what user is mysql running as? Thanks Subhro -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002 > 120611 10:55:52 [Warning] Can't create test file > /var/db/mysql/breakaway.lower-test > mysqld: Table 'mysql.plugin' doesn't exist > 120611 10:55:52 [ERROR] Can't open the mysql.plugin table. Please run > mysql_upgrade to create it. > 120611 10:55:52 InnoDB: The InnoDB memory heap is disabled > 120611 10:55:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins > 120611 10:55:52 InnoDB: Compressed tables use zlib 1.2.5 > 120611 10:55:52 InnoDB: Initializing buffer pool, size = 128.0M > 120611 10:55:52 InnoDB: Completed initialization of buffer pool > 120611 10:55:52 InnoDB: Operating system error number 13 in a file operation. > InnoDB: The error means mysqld does not have the access rights to > InnoDB: the directory. > InnoDB: File name ./ibdata1 > InnoDB: File operation call: 'create'. > InnoDB: Cannot continue operation. > > Running mysqld --verbose shows: > > basedir /usr/local > general-log-file/var/db/mysql/breakaway.log > > ls -aol /usr/local/libexec/mysqld > -rwxr-xr-x 1 root wheel - 9558944 Jun 11 10:40 /usr/local/libexec/mysqld > ls -dl /var/db/mysql > drwxr-xr-x 2 mysql mysql 512 Jun 11 10:31 /var/db/mysql > > cd / > find . -ls | grep my.cnf > > shows nothing. > > This looks like some kind of access / setuid problem, but I'm not sure what. > Suggestions? > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
mysqld startup issue
I've done the following after having a running system with a running mysql on it: moved user accounts, although no logical move: /usr/home/foo was => /hd1/foo now /usr/home => /hd1/home and /hd1/foo is now /hd1/home/foo repartitioned the SSD and restored the system from a dump taken prior to repartitioning. removed all ports and reinstalled them Unfortunately, mysqld won't start: 120611 10:55:52 [Warning] Can't create test file /var/db/mysql/breakaway.lower-test 120611 10:55:52 [Warning] Can't create test file /var/db/mysql/breakaway.lower-test mysqld: Table 'mysql.plugin' doesn't exist 120611 10:55:52 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 120611 10:55:52 InnoDB: The InnoDB memory heap is disabled 120611 10:55:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins 120611 10:55:52 InnoDB: Compressed tables use zlib 1.2.5 120611 10:55:52 InnoDB: Initializing buffer pool, size = 128.0M 120611 10:55:52 InnoDB: Completed initialization of buffer pool 120611 10:55:52 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'create'. InnoDB: Cannot continue operation. Running mysqld --verbose shows: basedir /usr/local general-log-file/var/db/mysql/breakaway.log ls -aol /usr/local/libexec/mysqld -rwxr-xr-x 1 root wheel - 9558944 Jun 11 10:40 /usr/local/libexec/mysqld ls -dl /var/db/mysql drwxr-xr-x 2 mysql mysql 512 Jun 11 10:31 /var/db/mysql cd / find . -ls | grep my.cnf shows nothing. This looks like some kind of access / setuid problem, but I'm not sure what. Suggestions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Startup from script
Thank you (all) for your information; I followed your suggestions and it all works flawless! best regards, Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Startup from script
In my crontab I define script 'do_daily.run': 30 23 * * * root /root/cronjobs/do_daily.run The content of this script (amongst others) is: rsync -avpog /etc /backup/$DATE/ Funny thing now is that in the output of the script, the following appears: /root/cronjobs/do_daily.run: rsync: not found file credentials of the script itself: -rwx-- 1 root wheel 246 Jun 20 2010 do_daily.run What do I oversee here? add PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin in the beginning of your crontab your default $PATH is NOT cron default $PATH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Startup from script
Jos Chrispijn writes: > The content of this script (amongst others) is: > rsync -avpog /etc /backup/$DATE/ > > Funny thing now is that in the output of the script, the following appears: > /root/cronjobs/do_daily.run: rsync: not found > > file credentials of the script itself: > -rwx-- 1 root wheel 246 Jun 20 2010 do_daily.run 1) rsync is a port. 2) by default, ports install executables to /usr/local/bin 3) by default, "do_daily_run" will inherit its environment - including PATH - from crontab(5) (system or per-user). 4) by default, the crontab PATH does not include /usr/local/bin. (There is a reason for this.) Recommended solution: provide the full path to rsync. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Startup from script
On Tue, 22 May 2012 13:50:10 +0200 Jos Chrispijn wrote: > I have this issue with running commands from a script: > > In my crontab I define script 'do_daily.run': > 30 23 * * * root > /root/cronjobs/do_daily.run > > The content of this script (amongst others) is: > rsync -avpog /etc /backup/$DATE/ > > Funny thing now is that in the output of the script, the following > appears: /root/cronjobs/do_daily.run: rsync: not found > > file credentials of the script itself: > -rwx-- 1 root wheel 246 Jun 20 2010 do_daily.run > You need to set PATH in the crontab or script, or use the full path for rsync. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Startup from script
I have this issue with running commands from a script: In my crontab I define script 'do_daily.run': 30 23 * * * root /root/cronjobs/do_daily.run The content of this script (amongst others) is: rsync -avpog /etc /backup/$DATE/ Funny thing now is that in the output of the script, the following appears: /root/cronjobs/do_daily.run: rsync: not found file credentials of the script itself: -rwx-- 1 root wheel 246 Jun 20 2010 do_daily.run What do I oversee here? kind regards, Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: webcamd startup problems
Hi, Webcamd is started by devd. In rc.conf, try: devd_enable="YES" --HPS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: webcamd startup problems
I'm having the exact same problem. Have been trying to get it resolved in the FreeBSD community forums with no luck. -- View this message in context: http://freebsd.1045724.n5.nabble.com/webcamd-startup-problems-tp3927737p5398421.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: startup postgresql 9.0.3
Jeff Hamann wrote: > I've installed and tested postgresql just fine on FreeBSD 8.2. > > I've been trying to get postgresql (the server) to start on bootup using > /etc/rc.conf system. Sometime quite a while back FreeBSD imported the rc.subr startup subsystem from NetBSD. > I'm using the script from the tarball (found in the > contrib/start-scripts/freebsd of postreges tarball) This script is not in rc.subr format, looks a tad "Linuxy" at first glance. > I can't seem to get it to work on FreeBSD 8.2 amd64 (I don't think the > arch is important here, but you never know). > > As instructed in the script, I've moved the file to > /usr/local/etc/rc.d/postgresql This is definitely the right location. There are some instructions on a couple of other things to look at first in the ports build output. These can be examined in the port directory for clues. > I've added the "postgresql_enable=YES" to /etc/rc/conf. As a non rc.subr script it will never pick up this variable. > I know I'm missing some magic here > (http://www.freebsd.org/doc/en_US.ISO8859-1/articles/rc- scripting/index.html > perhaps?) > > I've /usr/local/pgsql/bin./postgres --help'd too and can't seem to get > traction. If everything else seems OK, like you can start it without the script and all you need to do is convert the script over so it will start with boot, look over the port patchset and some of the other startup scripts. It's not too difficult once you see how the other rc.subr scripts are put together. I thought a sysvinit script would still work as a fallback as long as it was marked executable, and perhaps with a .sh at the end. I remember needing the .sh for a while and discovering they were supposed to work anyway without it. Upon investigation that turned out to be something I missed/ignored with mergemaster during a system update. Maybe this has fallen by the wayside. > Can you please help? I'm sure this is something simple I'm neglecting. I'm pretty "simple" myself. If I can install it with the ports system where all the hard stuff has been handled for me by people smarter than me, well, that's a no-brainer. :-) > Please don't respond with "Why don't you just use the ports collection?" My first inclination. Postgresql is a fairly complicated thing and using the ports to install it "makes it go". Too many other pressing issues... > There's reasons - like: > 1) need to build from source Uhmmm - ports build from source. > 3) it's for a tutorial - non-sequitur > 3) postgresql90-server isn't building. I would be more concerned by this. I just went to the postgresql90-server port and it built just fine. If it isn't for you it indicates other problems with your system. Another thing you'll find eventually, that when you don't use the ports system maintenance will soon become a nightmare. As a sysadmin I make it a point to not shoot myself in the foot. Building stuff from tarballs is for the birds from a sysadmins point of view. It's called: "Ready! Fire! Aim!" -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: startup postgresql 9.0.3
On Jun 16, 2011, at 10:26 AM, Jeff Hamann wrote: > I've installed and tested postgresql just fine on FreeBSD 8.2. I gather this means running the database manually via "postgres -D /usr/local/pgsql/data" works normally? > As instructed in the script, I've moved the file to > /usr/local/etc/rc.d/postgresql > > I've added the "postgresql_enable=YES" to /etc/rc/conf. Is /usr/local/etc/rc.d/postgresql executable? What does "/usr/local/etc/rc.d/postgresql start" do? (If you don't get a useful answer, running it via sh -x might be more informative.) > Please don't respond with "Why don't you just use the ports collection?" > There's reasons - like: 1) need to build from source, 3) it's for a tutorial, > and 3) postgresql90-server isn't building. You've counted to three rather oddly there. Obviously, building from ports is building from source. I don't see how the first "3)" is relevant, but the errors reported from the second "3)" might be more interesting. Regard, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
startup postgresql 9.0.3
I've installed and tested postgresql just fine on FreeBSD 8.2. I've been trying to get postgresql (the server) to start on bootup using /etc/rc.conf system. I'm using the script from the tarball (found in the contrib/start-scripts/freebsd of postreges tarball) I can't seem to get it to work on FreeBSD 8.2 amd64 (I don't think the arch is important here, but you never know). As instructed in the script, I've moved the file to /usr/local/etc/rc.d/postgresql I've added the "postgresql_enable=YES" to /etc/rc/conf. I know I'm missing some magic here (http://www.freebsd.org/doc/en_US.ISO8859-1/articles/rc-scripting/index.html perhaps?) I've /usr/local/pgsql/bin./postgres --help'd too and can't seem to get traction. Can you please help? I'm sure this is something simple I'm neglecting. Please don't respond with "Why don't you just use the ports collection?" There's reasons - like: 1) need to build from source, 3) it's for a tutorial, and 3) postgresql90-server isn't building. Respectfully, Jeff. Jeff Hamann, PhD PO Box 1421 Corvallis, Oregon 97339-1421 541-754-2457 jeff.hamann[at]forestinformatics[dot]com http://www.forestinformatics.com http://forufus.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: sguil-client startup problem
Paul, No worries, I had to deinstall tclX, ictl , iwidgets and sguil-client and reinstall them in the same order to make things work. Not touching the tcl8.5 installation. On the server side, Barnyard2 required an extra addition in the Makefile, referencing the --with-tcllib= location (after the mysql reference). Followed by a deinstall and install , resulting in a working snort -> barnyard2 -> sguil environment. Thanks for your time. Met vriendelijke groet / Kind regards, Danny van der Schaft -Oorspronkelijk bericht- Van: Paul Schmehl [mailto:pschmehl_li...@tx.rr.com] Verzonden: vrijdag 18 maart 2011 20:14 Aan: Schaft van der, D (Danny); freebsd-questions@freebsd.org Onderwerp: Re: sguil-client startup problem --On March 17, 2011 4:30:31 PM +0100 d.sch...@rn.rabobank.nl wrote: > I have a question regarding the installation and startup of sguil-client > on a 8.2 Generic OS. It seems that my installation requires an iwidget > extension when run with tclsh8.4 and receives an error when running > wish8.4: > > Error in startup script: can't read "0": no such variable while executing > Exec /usr/local/bin/wish8.4 "$0" "$@" line 5. > > I have all the required packages , I suppose > (tclX-8.4,tcl-8.4,tcllib,tcltls,tk8.4,ictl-3), also the iwidget extension > is installed... Strangely enough also version 8.5 is present on the > system, could that be a problem. Hopefully , there is someone who has > experienced the same or better yet, has an answer to my problem... > Apparently the default tcl install is now 8.5. Looks like I'm going to have to update the ports. You *may* be able to fix your problem by editing the sguil.tk file, although I'm not sure what other impacts that might have. The script calls wish8.4 explicitly, but that probably doesn't exist on your system. Change it to 8.5 and see if that fixes the problem. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell == Rabobank disclaimer: http://www.rabobank.nl/disclaimer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: sguil-client startup problem
--On March 17, 2011 4:30:31 PM +0100 d.sch...@rn.rabobank.nl wrote: I have a question regarding the installation and startup of sguil-client on a 8.2 Generic OS. It seems that my installation requires an iwidget extension when run with tclsh8.4 and receives an error when running wish8.4: Error in startup script: can't read "0": no such variable while executing Exec /usr/local/bin/wish8.4 "$0" "$@" line 5. I have all the required packages , I suppose (tclX-8.4,tcl-8.4,tcllib,tcltls,tk8.4,ictl-3), also the iwidget extension is installed... Strangely enough also version 8.5 is present on the system, could that be a problem. Hopefully , there is someone who has experienced the same or better yet, has an answer to my problem... Apparently the default tcl install is now 8.5. Looks like I'm going to have to update the ports. You *may* be able to fix your problem by editing the sguil.tk file, although I'm not sure what other impacts that might have. The script calls wish8.4 explicitly, but that probably doesn't exist on your system. Change it to 8.5 and see if that fixes the problem. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
webcamd startup problems
Hope someone can see what I missed here, as the topic says, webcamd doesn't start at boot. Logitec USB cameram product 0x08b2 vendor 0x046d, is plugged in, works wonderfully in skype-2.0.0.72,1, emesene-1.6.3, pwcview, etc.. grep webc /etc/rc.conf webcamd_enable="YES" -r-xr-xr-x 1 root wheel 775 Mar 8 19:35 /usr/local/etc/rc.d/webcamd grep cuse /boot/loader.conf cuse4bsd_load="YES" The camera doesn't show up when I boot the system, webcamd doesn't start. I have to run webcamd & to start it, and it happily prints out, Attached ugen2.2[0] to cuse unit 0 Creating /dev/video0 So, my question is, why isn't this starting at boot? -- I am currently away on leave, traveling through time and will be returning last week. Life is tough, but it's tougher when you're stupid. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
sguil-client startup problem
I have a question regarding the installation and startup of sguil-client on a 8.2 Generic OS. It seems that my installation requires an iwidget extension when run with tclsh8.4 and receives an error when running wish8.4: Error in startup script: can't read "0": no such variable while executing Exec /usr/local/bin/wish8.4 "$0" "$@" line 5. I have all the required packages , I suppose (tclX-8.4,tcl-8.4,tcllib,tcltls,tk8.4,ictl-3), also the iwidget extension is installed... Strangely enough also version 8.5 is present on the system, could that be a problem. Hopefully , there is someone who has experienced the same or better yet, has an answer to my problem... Reg, Danny van der Schaft == Rabobank disclaimer: http://www.rabobank.nl/disclaimer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
configuring mobile broadband at startup
Hi, I'm using cdce interface to get online. But before I can get IP address on my ue0 interface with dhclient, I need to power up and configure the GSM modem. At the moment I'm doing it by hand with cu(1) utility. How can I get it automated so that ue0 is running right after system startup? I know I can make a custom shell script but is there a proper way of doing it? Does the system provides some configuration mechanism at system startup time? Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Manage Bind9 through the web, PowerDNS crash my system at startup
Hello, My problem (PowerDNS crash my system at startup) have been solved by correcting the configuration of PowerDNS as follow: Edit /usr/local/etc/pdns/pdns.conf and be sure that : daemon=yes guardian=yes Thanks with best wishes. Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? Hello, Thank you for your reply. I thought you put your hand in my exact problem. When I start PowerDNS from command line using "/usr/local/etc/rc.d/pdns onestart" its running smooth. To make auto startup I just put this line pdns_enable="YES" to the end of /etc/rc.conf. Can you please highlight to me how and where to add the instruction for auto startup of PowerDNS to be sure it's starting after Mysql. Thank, and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" look at the require and provide lines of the rc scripts hello, this snap of my rc.conf sshd_enable="YES" ntpdate_enable="YES" apache22_enable="YES" named_enable="NO" mysql_enable="YES" mysql_dbdir="/usr/local/etc/mysql" sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" pdns_enable="YES" Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Manage Bind9 through the web, PowerDNS crash my system at startup
Hello. I am sorry if my comment sounds stupid... but It won't be WEBMIN an alternative for managing simple BIND operations? Jorge Biquez At 11:10 a.m. 07/01/2011, Sayed Nimer wrote: Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? Hello, Thank you for your reply. I thought you put your hand in my exact problem. When I start PowerDNS from command line using "/usr/local/etc/rc.d/pdns onestart" its running smooth. To make auto startup I just put this line pdns_enable="YES" to the end of /etc/rc.conf. Can you please highlight to me how and where to add the instruction for auto startup of PowerDNS to be sure it's starting after Mysql. Thank, and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" look at the require and provide lines of the rc scripts hello, this snap of my rc.conf sshd_enable="YES" ntpdate_enable="YES" apache22_enable="YES" named_enable="NO" mysql_enable="YES" mysql_dbdir="/usr/local/etc/mysql" sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" pdns_enable="YES" Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Manage Bind9 through the web, PowerDNS crash my system at startup
Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? Hello, Thank you for your reply. I thought you put your hand in my exact problem. When I start PowerDNS from command line using "/usr/local/etc/rc.d/pdns onestart" its running smooth. To make auto startup I just put this line pdns_enable="YES" to the end of /etc/rc.conf. Can you please highlight to me how and where to add the instruction for auto startup of PowerDNS to be sure it's starting after Mysql. Thank, and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" look at the require and provide lines of the rc scripts hello, this snap of my rc.conf sshd_enable="YES" ntpdate_enable="YES" apache22_enable="YES" named_enable="NO" mysql_enable="YES" mysql_dbdir="/usr/local/etc/mysql" sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" pdns_enable="YES" Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Manage Bind9 through the web, PowerDNS crash my system at startup
On 7 January 2011 15:53, Sayed Nimer wrote: > On Fri, Jan 7, 2011 at 8:39 AM, Sayed Nimer wrote: > > Hello, > I was looking for a solution to manage Bind9 DNS server through a web so I > can add/edit zone. > I thought PowerDNS/PowerAdmin would be a good solution for my requirements. > I successfully installed both PowerDNS/PowerAdmin and tested them was > working fine. > When I restart my box I found PowerDNS crash my system giving many errors > can't find mysqlserver. > Any suggestions for the requirement to manage Bind9 through the web, or the > PowerDNS problem. > Thanks and have a nice day. > > > Have you tried making sure that the MySQL daemon is started /BEFORE/ > PowerDNS and Apache is started? > > > > Hello, > > Thank you for your reply. I thought you put your hand in my exact problem. > > When I start PowerDNS from command line using "/usr/local/etc/rc.d/pdns > onestart" its running smooth. > > To make auto startup I just put this line pdns_enable="YES" to the end of > /etc/rc.conf. > > Can you please highlight to me how and where to add the instruction for > auto startup of PowerDNS to be sure it's starting after Mysql. > > Thank, and have a nice day. > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > look at the require and provide lines of the rc scripts ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Manage Bind9 through the web, PowerDNS crash my system at startup
On Fri, Jan 7, 2011 at 8:39 AM, Sayed Nimer wrote: Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? Hello, Thank you for your reply. I thought you put your hand in my exact problem. When I start PowerDNS from command line using "/usr/local/etc/rc.d/pdns onestart" its running smooth. To make auto startup I just put this line pdns_enable="YES" to the end of /etc/rc.conf. Can you please highlight to me how and where to add the instruction for auto startup of PowerDNS to be sure it's starting after Mysql. Thank, and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Manage Bind9 through the web, PowerDNS crash my system at startup
On Fri, Jan 7, 2011 at 8:39 AM, Sayed Nimer wrote: > Hello, > I was looking for a solution to manage Bind9 DNS server through a web so I > can add/edit zone. > I thought PowerDNS/PowerAdmin would be a good solution for my requirements. > I successfully installed both PowerDNS/PowerAdmin and tested them was > working fine. > When I restart my box I found PowerDNS crash my system giving many errors > can't find mysqlserver. > Any suggestions for the requirement to manage Bind9 through the web, or the > PowerDNS problem. > Thanks and have a nice day. > Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Manage Bind9 through the web, PowerDNS crash my system at startup
Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ejabberd won't startup
Hello Panagiotis and list, > I believe we are facing the same issue. Our setup is ejabberd-2.1.5 in > a FreeBSD 7.3 amd64 jail and the workaround we found is running an > older version of erlang (erlang-r13b04_3,1). You can find the old > erlang port files in the FreeBSD CVS repository or here: > > http://noc.ntua.gr/~christia/erlang.tgz it seems a solution came up to run Erlang 14B in a Jail. A few minutes ago, Michael from the Erlang tribe provied a quick patch for Erlang 14B to disable the checks causing the issue with erlang 14B in Jails. Here's his quick patch: > diff --git a/erts/epmd/src/epmd_srv.c b/erts/epmd/src/epmd_srv.c > index ef471a4..e2cc2dc 100644 > --- a/erts/epmd/src/epmd_srv.c > +++ b/erts/epmd/src/epmd_srv.c > @@ -766,6 +766,9 @@ static int conn_open(EpmdVars *g,int fd) >dbg_tty_printf(g,2,(s->local_peer) ? "Local peer connected" : >"Non-local peer connected"); > > + /* XXX allow local messages from all clients */ > + s->local_peer = EPMD_TRUE; > + >s->want = 0; /* Currently unknown */ >s->got = 0; >s->mod_time = current_time(g); /* Note activity */ He also announced to make a better patch in a few days. Also the Erlang folks might offer a future option to disable the check or provide another possibility to propperly run Erlang and Erlang programs (such as ejabberd) in a Jail. Hope this helps kind regards Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ejabberd won't startup
update on the issue with Jails and Erlang 14B:
> > Hi everybody dealing with ejabberd and/or erlang in a FreeBSD8-Jail !
> >
> > I've built the ejabberd port (with ODBC support / the Erlang MySQL
> > driver) two days ago but can't get it to run.
> >
> > # ejabberdctl start
> >
> > spits out a huge bunch of Erlang error messages (unreadable for most
> > humans), obviously saying that it can't connect properly to the
> > loopback interface on Port 4369 (respectively connects but then
> > immediately stops, causing a crash dump and not able to "register it's
> > node"). Tcpdump shows 8 pakets captured when pointing to the lo0
> > interface.
> >
> > The jail is an ordinary Jail with no special configuration (just 1 IP
> > and a proper hostname, running Postfix/Dovecot with MySQL just fine).
> > PF or it's ruleset too seems not to be the cause as Erlang's behaviour
> > is the same even with a switched off PF. Restarting the Jail and
> > triple-checking it's parameters did not help too.
> >
> > As the error can be reproduced solely with Erlang (without even
> > starting ejabberd), the ejabberd.cfg file however does not seem to
> > play any role.
> >
> > I was told, this actually was an Erlang issue and so I first went to
> > the Erlang folks (erlang mailing list). At least until now, they
> > unfortunately could not help me making a real step.
> >
> > So, I got stuck and now am in search for people successfully running
> > ejabberd in a Jail. I have seen reports from the web on success and
> > even I too had a test installation in a Jail running half a year ago
> > (unfortunately did not note all details before I wiped that testing
> > machine).
> >
> > My suggestion is, it might have something to do with the file
> > /usr/locaal/etc/ejabberd/inetrc
> > (responsible for name resolution for Erlang)
> >
> > So, are there any Jail/ejabberd experts out there ?
> > Or just people having it up and running ?
>
> Hello,
>
> I believe we are facing the same issue. Our setup is ejabberd-2.1.5 in
> a FreeBSD 7.3 amd64 jail and the workaround we found is running an
> older version of erlang (erlang-r13b04_3,1). You can find the old
> erlang port files in the FreeBSD CVS repository or here:
>
> http://noc.ntua.gr/~christia/erlang.tgz
>
> Regards,
> Panagiotis
I experienced the phenomenon with Erlang 14B:
# erl
Erlang R14B (erts-5.8.1) [source] [smp:4:4] [rq:4] [async-threads:0] [hipe]
[kernel-poll:false]
Eshell V5.8.1
The error message then is:
> ejabberd Start:
>
> # ejabberdctl status
> {error_logger,{{2010,11,16},{9,56,20}},"Protocol: ~p: register error:
~p~n",
> ["inet_tcp",{{badmatch,{error,epmd_close}},[{inet_tcp_dist,listen,1},
but the same pops up when just starting up an Erlang node without any
ejabberd.
From the Erlang mailing list I learned:
"epmd in R14B was changed to allow some messages (like name registrations)
only from 127/8. "
So, this might explain why there are those problems with the new Erlang in a
Jail.
The most recent report of a working Erlang/ejabberd in a Jail I have found
via Google is from around Janary 2010.
So, if there is no newer positiv experience with Erlang 14B in a Jail it
might be a good idea to provide a Port for ejabberd with an older Erlang.
But still I'm not sure whether or not it is possible to get Erlang 14B to
run in a Jail.
Any further hints / ideas out there ?
Tom
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ejabberd won't startup
Hi everybody dealing with ejabberd and/or erlang in a FreeBSD8-Jail ! I've built the ejabberd port (with ODBC support / the Erlang MySQL driver) two days ago but can't get it to run. # ejabberdctl start spits out a huge bunch of Erlang error messages (unreadable for most humans), obviously saying that it can't connect properly to the loopback interface on Port 4369 (respectively connects but then immediately stops, causing a crash dump and not able to "register it's node"). Tcpdump shows 8 pakets captured when pointing to the lo0 interface. The jail is an ordinary Jail with no special configuration (just 1 IP and a proper hostname, running Postfix/Dovecot with MySQL just fine). PF or it's ruleset too seems not to be the cause as Erlang's behaviour is the same even with a switched off PF. Restarting the Jail and triple-checking it's parameters did not help too. As the error can be reproduced solely with Erlang (without even starting ejabberd), the ejabberd.cfg file however does not seem to play any role. I was told, this actually was an Erlang issue and so I first went to the Erlang folks (erlang mailing list). At least until now, they unfortunately could not help me making a real step. So, I got stuck and now am in search for people successfully running ejabberd in a Jail. I have seen reports from the web on success and even I too had a test installation in a Jail running half a year ago (unfortunately did not note all details before I wiped that testing machine). My suggestion is, it might have something to do with the file /usr/locaal/etc/ejabberd/inetrc (responsible for name resolution for Erlang) So, are there any Jail/ejabberd experts out there ? Or just people having it up and running ? kind regards Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPFW at startup.
In freebsd-questions Digest, Vol 337, Issue 2, Message: 26
On Mon, 15 Nov 2010 10:52:41 -0800 Dave Robison wrote:
> I haven't seen someone use "firewall_type" as a path to the config file.
It's not so uncommon. Anyone who's based their ruleset on the handbook
section on IPFW will likely be using this method, and Grant has used it
correctly. This is only applicable where $firewall_script is set to
'/etc/rc.firewall', but that is the default in /etc/defaults/rc.conf
> If you check the default rc.firewall file, you will see several types of
> default firewall settings, such as "open" and "closed". You want to set
> "firewall_type" in rc.conf to be "open" or whatever your firewall type
> is in /etc/rc.firewall.
Please note the last section in rc.firewall, which specifically tests
whether $firewall_type is a readable file, and if so, passes that file
as an argument to ipfw(8) (qv).
*)
if [ -r "${firewall_type}" ]; then
${fwcmd} ${firewall_flags} ${firewall_type}
fi
;;
esac
Also note that in this case, the file is not a shell script, but a set
of arguments to the ipfw command. Grant's set is in the correct format.
> You can probably get away with editing your existing rc.firewall to
> include a firewall type, such as "custom", then defining firewall_type
> as "custom" in /etc/rc.conf.
You could, but it's not necessary. In the olden days you more or less
had to do that, but nowadays you can specify parameters for the client,
simple and workstation types, so you can get a minimal reasonably safe
and effective firewall going, at least for starters, just using rc.conf
variables. This also means you can avoid messing with rc.firewall, so
that system updates will properly bring in any changes and additions.
The documentation for this is so far really only in /etc/rc.firewall
itself and in /etc/defaults/rc.conf .. perhaps one day $someone will
re-write the Handbook IPFW section; meanwhile ipfw(8) is definitive.
You can also start out using one of the builtin types, then save it to a
file with 'ipfw list >file', then modify things it there, add comments
etc, then specify that file as firewall_type henceforth. Or, as Chuck
has shown, you can get really fancy and use some preprocessor :)
cheers, Ian
PS: Please don't top-post on FreeBSD lists, and if at all possible avoid
posting multiple disclaimers, that are in any case entirely inapplicable
to public list postings.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPFW at startup.
On Mon, Nov 15, 2010 at 10:52:41AM -0800, Dave Robison wrote: > I haven't seen someone use "firewall_type" as a path to the config > file. If you check the default rc.firewall file, you will see several > types of default firewall settings, such as "open" and "closed". You > want to set "firewall_type" in rc.conf to be "open" or whatever your > firewall type is in /etc/rc.firewall. What he needs to do is use firewall_script="/etc/ipfw.rules" rather than firewall_type= -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPFW at startup.
Hi-- On Nov 15, 2010, at 10:52 AM, Dave Robison wrote: > I haven't seen someone use "firewall_type" as a path to the config file. If > you check the default rc.firewall file, you will see several types of default > firewall settings, such as "open" and "closed". You want to set > "firewall_type" in rc.conf to be "open" or whatever your firewall type is in > /etc/rc.firewall. If you set both of these in /etc/rc.conf: firewall_type="/etc/FW1.ipfw" firewall_flags="-p cpp" ...then /etc/FW1_firewall will be processed by cpp (ie, so you can use #include directives, C-style macros, etc) before going to IPFW. This is probably more obscure than useful for human-editted rulesets :-), but for automated processing and accumulating lists of bad hosts via denyhosts or similar, it can be useful Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPFW at startup.
I haven't seen someone use "firewall_type" as a path to the config file.
If you check the default rc.firewall file, you will see several types of
default firewall settings, such as "open" and "closed". You want to set
"firewall_type" in rc.conf to be "open" or whatever your firewall type
is in /etc/rc.firewall.
You can probably get away with editing your existing rc.firewall to
include a firewall type, such as "custom", then defining firewall_type
as "custom" in /etc/rc.conf.
Enjoy,
On 11/14/10 14:50, Grant Peel wrote:
Hi all,
I seem to have one server that does not flush the /etc/rc.firewall
rules when the script taken from "firewall_type" starts up. That is
to say when I boot the machine, 3 rules seem to be still in the list
when I do an ipfw -a list. Those three rules appear to be from the
/etc.rc.firewall script. The rules from my /etc/ipfw.rules file DO get
loaded.
Here are the three rules (100, 200, and 300), from /etc/rc.firewall.
setup_loopback () {
# Only in rare cases do you want to change these rules
#
${fwcmd} add 100 pass all from any to any via lo0
${fwcmd} add 200 deny all from any to 127.0.0.0/8
${fwcmd} add 300 deny ip from 127.0.0.0/8 to any
Here is my /etc/rc,conf setup:
firewall_enable="YES"
firewall_logging="YES"
firewall_type="/etc/ipfw.rules"
Here is my /etc/ipfw.rules:
enterprise# more /etc/ipfw.rules
# Loopback
add 1 allow ip from any to any via lo0
# Office and Home
add 00200 allow ip from xxx xxx xxx xxx xxx to any
add 00201 allow ip from any to xxx xxx xxx xxx
add 00202 allow all from xxx xxx xxx xxx to any
add 00203 allow all from any to xxx xxx xxx xxx
# Allow fxp0 out
add 00204 allow all from any to any out
# Allow local net
add 02000 allow ip from any to any via fxp1
# email
add 04000 allow all from xxx xxx xxx xxx to any
add 04010 allow all from any to xxx xxx xxx xxx
add 04020 allow all from xxx xxx xxx xxx to any
add 04030 allow all from any to xxx xxx xxx xxx
add 04040 allow tcp from any to any 25,587
add 04050 allow tcp from any 25,587 to any
# Bruteblock
add 08000 deny ip from table(1) to me
add 08001 deny ip from me to table(1)
add 09050 allow udp from any to any 53 in
# Email Test
add 09100 allow icmp from any to any icmptypes
0,3,4,5,8,9,10,11,12,13,14,15,16,17,18
add 65535 deny ip from any to any
Oddly enough, I have several machies that are setup identicly and this
is the only one that has stikky rules from /etc/rc.firewall.
Any one have any idea what knob might have been turned that causes the
sticky startup rules?
-Grant
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscr...@freebsd.org"
--
Dave Robison
Sales Solution Architect II
FIS Banking Solutions
510/621-2089 (w)
530/518-5194 (c)
510/621-2020 (f)
da...@vicor.com
This message contains confidential and proprietary information
of the sender, and is intended only for the person(s) to whom
it is addressed. Any use, distribution, copying or disclosure
by any other person is strictly prohibited. If you have
received this message in error, please notify the e-mail sender
immediately, and delete the original message without making a
copy.
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
_
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPFW at startup.
Здравствуйте, Grant.
Вы писали 15 ноября 2010 г., 0:50:47:
GP> Hi all,
GP> I seem to have one server that does not flush the /etc/rc.firewall rules
GP> when the script taken from "firewall_type" starts up. That is to say when I
GP> boot the machine, 3 rules seem to be still in the list when I do an ipfw -a
GP> list. Those three rules appear to be from the /etc.rc.firewall script. The
GP> rules from my /etc/ipfw.rules file DO get loaded.
GP> Here are the three rules (100, 200, and 300), from /etc/rc.firewall.
GP> setup_loopback () {
GP>
GP> # Only in rare cases do you want to change these rules
GP> #
GP> ${fwcmd} add 100 pass all from any to any via lo0
GP> ${fwcmd} add 200 deny all from any to 127.0.0.0/8
GP> ${fwcmd} add 300 deny ip from 127.0.0.0/8 to any
GP> Here is my /etc/rc,conf setup:
GP> firewall_enable="YES"
GP> firewall_logging="YES"
GP> firewall_type="/etc/ipfw.rules"
you need "firewall_script" variable
GP> Here is my /etc/ipfw.rules:
GP> enterprise# more /etc/ipfw.rules
GP> # Loopback
GP> add 1 allow ip from any to any via lo0
GP> # Office and Home
GP> add 00200 allow ip from xxx xxx xxx xxx xxx to any
GP> add 00201 allow ip from any to xxx xxx xxx xxx
GP> add 00202 allow all from xxx xxx xxx xxx to any
GP> add 00203 allow all from any to xxx xxx xxx xxx
GP> # Allow fxp0 out
GP> add 00204 allow all from any to any out
GP> # Allow local net
GP> add 02000 allow ip from any to any via fxp1
GP> # email
GP> add 04000 allow all from xxx xxx xxx xxx to any
GP> add 04010 allow all from any to xxx xxx xxx xxx
GP> add 04020 allow all from xxx xxx xxx xxx to any
GP> add 04030 allow all from any to xxx xxx xxx xxx
GP> add 04040 allow tcp from any to any 25,587
GP> add 04050 allow tcp from any 25,587 to any
GP> # Bruteblock
GP> add 08000 deny ip from table(1) to me
GP> add 08001 deny ip from me to table(1)
GP> add 09050 allow udp from any to any 53 in
GP> # Email Test
GP> add 09100 allow icmp from any to any icmptypes
GP> 0,3,4,5,8,9,10,11,12,13,14,15,16,17,18
GP> add 65535 deny ip from any to any
GP> Oddly enough, I have several machies that are setup identicly and this is
GP> the only one that has stikky rules from /etc/rc.firewall.
GP> Any one have any idea what knob might have been turned that causes the
GP> sticky startup rules?
GP> -Grant
GP> ___
GP> freebsd-questions@freebsd.org mailing list
GP> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
GP> To unsubscribe, send any mail to
GP> "freebsd-questions-unsubscr...@freebsd.org"
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPFW at startup.
In freebsd-questions Digest, Vol 337, Issue 1, Message: 15
On Sun, 14 Nov 2010 17:50:47 -0500 "Grant Peel" wrote:
>
> I seem to have one server that does not flush the /etc/rc.firewall rules
> when the script taken from "firewall_type" starts up. That is to say when I
> boot the machine, 3 rules seem to be still in the list when I do an ipfw -a
> list. Those three rules appear to be from the /etc.rc.firewall script. The
> rules from my /etc/ipfw.rules file DO get loaded.
>
> Here are the three rules (100, 200, and 300), from /etc/rc.firewall.
>
> setup_loopback () {
>
> # Only in rare cases do you want to change these rules
> #
> ${fwcmd} add 100 pass all from any to any via lo0
> ${fwcmd} add 200 deny all from any to 127.0.0.0/8
> ${fwcmd} add 300 deny ip from 127.0.0.0/8 to any
>
> Here is my /etc/rc,conf setup:
>
> firewall_enable="YES"
> firewall_logging="YES"
> firewall_type="/etc/ipfw.rules"
>
> Here is my /etc/ipfw.rules:
>
> enterprise# more /etc/ipfw.rules
> # Loopback
> add 1 allow ip from any to any via lo0
> # Office and Home
Ok, looking through your /etc/rc.firewall you should find:
# Flush out the list before we begin.
#
${fwcmd} -f flush
setup_loopback
which installs those rules straight after the flush. Browsing bits of
http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.firewall shows the last
version that does NOT run setup_loopback in ALL cases is RELENG_6.
Anyway, apart from the fact that rules 200 and 300 are worth having, all
you need to do to remove those rules is to make your first rule:
-f flush
I'll refrain from comment on your ruleset, except that:
> add 65535 deny ip from any to any
you can't actually override the default rule, which is either 'deny' or
'allow' according to the value of net.inet.ip.fw.default_to_accept which
depends on a kernel build option, so you might use say 65000 to be sure.
> Oddly enough, I have several machies that are setup identicly and this is
> the only one that has stikky rules from /etc/rc.firewall.
>
> Any one have any idea what knob might have been turned that causes the
> sticky startup rules?
If those systems are >= 7.0, maybe they have an older /etc/rc.firewall?
cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPFW at startup.
It's not a great idea to hack the rc.d scripts, they can be clobbered when updating. Chris Sorry for top-posting, Android won't let me quote, but K-9 can't yet do threading. On 15 Nov 2010 08:45, "Wojciech Puchar" wrote: simply edit /etc/rc.d/ipfw and make it doing only what you want. On Sun, 14 Nov 2010, Grant Peel wrote: > Hi all, > > I seem to have one server that does not flus... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPFW at startup.
simply edit /etc/rc.d/ipfw and make it doing only what you want.
On Sun, 14 Nov 2010, Grant Peel wrote:
Hi all,
I seem to have one server that does not flush the /etc/rc.firewall rules when
the script taken from "firewall_type" starts up. That is to say when I boot
the machine, 3 rules seem to be still in the list when I do an ipfw -a list.
Those three rules appear to be from the /etc.rc.firewall script. The rules
from my /etc/ipfw.rules file DO get loaded.
Here are the three rules (100, 200, and 300), from /etc/rc.firewall.
setup_loopback () {
# Only in rare cases do you want to change these rules
#
${fwcmd} add 100 pass all from any to any via lo0
${fwcmd} add 200 deny all from any to 127.0.0.0/8
${fwcmd} add 300 deny ip from 127.0.0.0/8 to any
Here is my /etc/rc,conf setup:
firewall_enable="YES"
firewall_logging="YES"
firewall_type="/etc/ipfw.rules"
Here is my /etc/ipfw.rules:
enterprise# more /etc/ipfw.rules
# Loopback
add 1 allow ip from any to any via lo0
# Office and Home
add 00200 allow ip from xxx xxx xxx xxx xxx to any
add 00201 allow ip from any to xxx xxx xxx xxx
add 00202 allow all from xxx xxx xxx xxx to any
add 00203 allow all from any to xxx xxx xxx xxx
# Allow fxp0 out
add 00204 allow all from any to any out
# Allow local net
add 02000 allow ip from any to any via fxp1
# email
add 04000 allow all from xxx xxx xxx xxx to any
add 04010 allow all from any to xxx xxx xxx xxx
add 04020 allow all from xxx xxx xxx xxx to any
add 04030 allow all from any to xxx xxx xxx xxx
add 04040 allow tcp from any to any 25,587
add 04050 allow tcp from any 25,587 to any
# Bruteblock
add 08000 deny ip from table(1) to me
add 08001 deny ip from me to table(1)
add 09050 allow udp from any to any 53 in
# Email Test
add 09100 allow icmp from any to any icmptypes
0,3,4,5,8,9,10,11,12,13,14,15,16,17,18
add 65535 deny ip from any to any
Oddly enough, I have several machies that are setup identicly and this is the
only one that has stikky rules from /etc/rc.firewall.
Any one have any idea what knob might have been turned that causes the sticky
startup rules?
-Grant
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPFW at startup.
Hi all,
I seem to have one server that does not flush the /etc/rc.firewall rules
when the script taken from "firewall_type" starts up. That is to say when I
boot the machine, 3 rules seem to be still in the list when I do an ipfw -a
list. Those three rules appear to be from the /etc.rc.firewall script. The
rules from my /etc/ipfw.rules file DO get loaded.
Here are the three rules (100, 200, and 300), from /etc/rc.firewall.
setup_loopback () {
# Only in rare cases do you want to change these rules
#
${fwcmd} add 100 pass all from any to any via lo0
${fwcmd} add 200 deny all from any to 127.0.0.0/8
${fwcmd} add 300 deny ip from 127.0.0.0/8 to any
Here is my /etc/rc,conf setup:
firewall_enable="YES"
firewall_logging="YES"
firewall_type="/etc/ipfw.rules"
Here is my /etc/ipfw.rules:
enterprise# more /etc/ipfw.rules
# Loopback
add 1 allow ip from any to any via lo0
# Office and Home
add 00200 allow ip from xxx xxx xxx xxx xxx to any
add 00201 allow ip from any to xxx xxx xxx xxx
add 00202 allow all from xxx xxx xxx xxx to any
add 00203 allow all from any to xxx xxx xxx xxx
# Allow fxp0 out
add 00204 allow all from any to any out
# Allow local net
add 02000 allow ip from any to any via fxp1
# email
add 04000 allow all from xxx xxx xxx xxx to any
add 04010 allow all from any to xxx xxx xxx xxx
add 04020 allow all from xxx xxx xxx xxx to any
add 04030 allow all from any to xxx xxx xxx xxx
add 04040 allow tcp from any to any 25,587
add 04050 allow tcp from any 25,587 to any
# Bruteblock
add 08000 deny ip from table(1) to me
add 08001 deny ip from me to table(1)
add 09050 allow udp from any to any 53 in
# Email Test
add 09100 allow icmp from any to any icmptypes
0,3,4,5,8,9,10,11,12,13,14,15,16,17,18
add 65535 deny ip from any to any
Oddly enough, I have several machies that are setup identicly and this is
the only one that has stikky rules from /etc/rc.firewall.
Any one have any idea what knob might have been turned that causes the
sticky startup rules?
-Grant
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: rc startup script - daemon: failed to set user environment
On Wed, Nov 3, 2010 at 12:47 PM, Frank Shute wrote:
> On Wed, Nov 03, 2010 at 08:55:45AM +0200, Valentin Bud wrote:
> >
> > Hello community,
> >
> > I am trying to build a startup script for an application built from
> source
> > code. The application name is SOGo (sogo.nu).
> >
> > I will attach the rc script and the error I receive when I run it.
> >
> > #!/bin/sh
> > #
> > #
> > # PROVIDE: sogod
> > # REQUIRE: memcached
> > #
> > # Add the following lines to /etc/rc.conf to enable sogod:
> > #
> > # sogod_enable (bool): Set it to "YES" to enable sogod.
> > # Default is "NO"
> > #
> > #
> >
> > . /etc/rc.subr
> >
> > name="sogod"
> > rcvar=`set_rcvar`
> >
> > load_rc_config ${name}
> >
> > : ${sogod_enable="NO"}
> > : ${sogod_user="sogo"}
> > : ${sogod_workers="-WOWorkersCount 1"}
> > : ${sogod_command="/usr/local/GNUstep/Local/Tools/Admin/sogod"}
> > : ${sogod_logfile="/var/log/sogo/sogo.log"}
> >
> > pidfile="/var/run/sogo/sogo.pid"
> > command="/usr/sbin/daemon"
> > command_args="-f -p ${pidfile} -u ${sogod_user} ${sogod_command}
> > ${sogod_workers} -WOPidFile ${pidfile} -WOLogFile ${sogod_logfile}"
> >
> > start_precmd="${name}_prestart"
> >
> > sogod_prestart() {
> > if [ ! -d `dirname ${pidfile}` ]; then
> > mkdir `dirname ${pidfile}` >/dev/null 2>&1 && chown
> > ${sogod_user} `dirname ${pidfile}`
> > fi
> > if [ ! -d `dirname ${sogod_logfile}` ]; then
> > mkdir `dirname ${sogod_logfile}` >/dev/null 2>&1
> > touch ${sogod_logfile} && chown ${sogod_user}
> > ${sogod_logfile}
> > fi
> > if [ -z ${GNUSTEP_SYSTEM_ROOT} ]; then
> > . /usr/local/GNUstep/System/Library/Makefiles/GNUstep.sh
> > fi
> > }
> >
> > run_rc_command "$1"
> >
> > The sogo daemon requires memcached running to start and the
> > file ${sogod_logfile}
> > to be readable by ${sogod_user}. I also requires the
> > directory /var/run/sogo/ to be read/write
> > by ${sogod_user} so it can write the PID file. The GNUstep.sh makefile
> must
> > be loaded
> > so it can run properly.
> >
> > The other command_args are the startup arguments sogod takes.
> >
> > memcached is already started:
> > sogo# sockstat | grep memcached
> > nobody memcached 71167 16 tcp4 172.31.32.6:11211 *:*
> > nobody memcached 71167 17 udp4 172.31.32.6:11211 *:*
> >
> > sogod is enabled is /etc/rc.conf
> > # /usr/local/etc/rc.d/sogod rcvar
> > # sogod
> > #
> > sogod_enable="YES"
> > # (default: "")
> >
> > This is the error I receive when I try to start sogod
> > sogo# /usr/local/etc/rc.d/sogod start
> > Starting sogod.
> > daemon: failed to set user environment
> > /usr/local/etc/rc.d/sogod: WARNING: failed to start sogod
> >
> > This is the first rc script I write. What can I do to debug the problem
> > further?
> >
> > Thank you and have a great day,
> > v
> > --
> > network warrior
>
> Starting with the obvious, did you create a sogo userID with adduser(8)?
> You want to give it nologin as a shell. It will also want a group.
>
>
> Regards,
>
> --
>
> Frank
>
> Contact info: http://www.shute.org.uk/misc/contact.html
>
>
> Hello Mr. Frank,
Yes I did.
sogo# id sogo
uid=1001(sogo) gid=1001(sogo) groups=1001(sogo)
Thank you,
v
--
network warrior
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: rc startup script - daemon: failed to set user environment
On Wed, Nov 03, 2010 at 08:55:45AM +0200, Valentin Bud wrote:
>
> Hello community,
>
> I am trying to build a startup script for an application built from source
> code. The application name is SOGo (sogo.nu).
>
> I will attach the rc script and the error I receive when I run it.
>
> #!/bin/sh
> #
> #
> # PROVIDE: sogod
> # REQUIRE: memcached
> #
> # Add the following lines to /etc/rc.conf to enable sogod:
> #
> # sogod_enable (bool): Set it to "YES" to enable sogod.
> # Default is "NO"
> #
> #
>
> . /etc/rc.subr
>
> name="sogod"
> rcvar=`set_rcvar`
>
> load_rc_config ${name}
>
> : ${sogod_enable="NO"}
> : ${sogod_user="sogo"}
> : ${sogod_workers="-WOWorkersCount 1"}
> : ${sogod_command="/usr/local/GNUstep/Local/Tools/Admin/sogod"}
> : ${sogod_logfile="/var/log/sogo/sogo.log"}
>
> pidfile="/var/run/sogo/sogo.pid"
> command="/usr/sbin/daemon"
> command_args="-f -p ${pidfile} -u ${sogod_user} ${sogod_command}
> ${sogod_workers} -WOPidFile ${pidfile} -WOLogFile ${sogod_logfile}"
>
> start_precmd="${name}_prestart"
>
> sogod_prestart() {
> if [ ! -d `dirname ${pidfile}` ]; then
> mkdir `dirname ${pidfile}` >/dev/null 2>&1 && chown
> ${sogod_user} `dirname ${pidfile}`
> fi
> if [ ! -d `dirname ${sogod_logfile}` ]; then
> mkdir `dirname ${sogod_logfile}` >/dev/null 2>&1
> touch ${sogod_logfile} && chown ${sogod_user}
> ${sogod_logfile}
> fi
> if [ -z ${GNUSTEP_SYSTEM_ROOT} ]; then
> . /usr/local/GNUstep/System/Library/Makefiles/GNUstep.sh
> fi
> }
>
> run_rc_command "$1"
>
> The sogo daemon requires memcached running to start and the
> file ${sogod_logfile}
> to be readable by ${sogod_user}. I also requires the
> directory /var/run/sogo/ to be read/write
> by ${sogod_user} so it can write the PID file. The GNUstep.sh makefile must
> be loaded
> so it can run properly.
>
> The other command_args are the startup arguments sogod takes.
>
> memcached is already started:
> sogo# sockstat | grep memcached
> nobody memcached 71167 16 tcp4 172.31.32.6:11211 *:*
> nobody memcached 71167 17 udp4 172.31.32.6:11211 *:*
>
> sogod is enabled is /etc/rc.conf
> # /usr/local/etc/rc.d/sogod rcvar
> # sogod
> #
> sogod_enable="YES"
> # (default: "")
>
> This is the error I receive when I try to start sogod
> sogo# /usr/local/etc/rc.d/sogod start
> Starting sogod.
> daemon: failed to set user environment
> /usr/local/etc/rc.d/sogod: WARNING: failed to start sogod
>
> This is the first rc script I write. What can I do to debug the problem
> further?
>
> Thank you and have a great day,
> v
> --
> network warrior
Starting with the obvious, did you create a sogo userID with adduser(8)?
You want to give it nologin as a shell. It will also want a group.
Regards,
--
Frank
Contact info: http://www.shute.org.uk/misc/contact.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
rc startup script - daemon: failed to set user environment
Hello community,
I am trying to build a startup script for an application built from source
code. The application name is SOGo (sogo.nu).
I will attach the rc script and the error I receive when I run it.
#!/bin/sh
#
#
# PROVIDE: sogod
# REQUIRE: memcached
#
# Add the following lines to /etc/rc.conf to enable sogod:
#
# sogod_enable (bool): Set it to "YES" to enable sogod.
# Default is "NO"
#
#
. /etc/rc.subr
name="sogod"
rcvar=`set_rcvar`
load_rc_config ${name}
: ${sogod_enable="NO"}
: ${sogod_user="sogo"}
: ${sogod_workers="-WOWorkersCount 1"}
: ${sogod_command="/usr/local/GNUstep/Local/Tools/Admin/sogod"}
: ${sogod_logfile="/var/log/sogo/sogo.log"}
pidfile="/var/run/sogo/sogo.pid"
command="/usr/sbin/daemon"
command_args="-f -p ${pidfile} -u ${sogod_user} ${sogod_command}
${sogod_workers} -WOPidFile ${pidfile} -WOLogFile ${sogod_logfile}"
start_precmd="${name}_prestart"
sogod_prestart() {
if [ ! -d `dirname ${pidfile}` ]; then
mkdir `dirname ${pidfile}` >/dev/null 2>&1 && chown
${sogod_user} `dirname ${pidfile}`
fi
if [ ! -d `dirname ${sogod_logfile}` ]; then
mkdir `dirname ${sogod_logfile}` >/dev/null 2>&1
touch ${sogod_logfile} && chown ${sogod_user}
${sogod_logfile}
fi
if [ -z ${GNUSTEP_SYSTEM_ROOT} ]; then
. /usr/local/GNUstep/System/Library/Makefiles/GNUstep.sh
fi
}
run_rc_command "$1"
The sogo daemon requires memcached running to start and the
file ${sogod_logfile}
to be readable by ${sogod_user}. I also requires the
directory /var/run/sogo/ to be read/write
by ${sogod_user} so it can write the PID file. The GNUstep.sh makefile must
be loaded
so it can run properly.
The other command_args are the startup arguments sogod takes.
memcached is already started:
sogo# sockstat | grep memcached
nobody memcached 71167 16 tcp4 172.31.32.6:11211 *:*
nobody memcached 71167 17 udp4 172.31.32.6:11211 *:*
sogod is enabled is /etc/rc.conf
# /usr/local/etc/rc.d/sogod rcvar
# sogod
#
sogod_enable="YES"
# (default: "")
This is the error I receive when I try to start sogod
sogo# /usr/local/etc/rc.d/sogod start
Starting sogod.
daemon: failed to set user environment
/usr/local/etc/rc.d/sogod: WARNING: failed to start sogod
This is the first rc script I write. What can I do to debug the problem
further?
Thank you and have a great day,
v
--
network warrior
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem running custom startup script at proper time
On Mon, Sep 20, 2010 at 09:00, Robert Bonomi wrote: >> From owner-freebsd-questi...@freebsd.org Sun Sep 19 16:37:49 2010 >> From: Aaron >> Date: Sun, 19 Sep 2010 14:39:08 -0700 >> To: freebsd-questions@freebsd.org >> Subject: Re: Problem running custom startup script at proper time >> >> Doh! Forgot to reply to the mailing list. >> >> >> Nope, that didn't work either. Darn. Maybe I'll just have to modify >> the /etc/rc.d/zfs script to run the for loop first :( > > How about just modifying the REQUIRE header on it to include 'gnop' > the sequencer that selects the order to run rc.d things in sorts based > on the REQUIRE/PROVIDES dependencies. > Nope, that didn't fix it. I even tried editing /etc/rc.d/zfs and included the gnop commands in the zfs_start(). The gnop still started up _after_ the ZFS in dmesg. However, I did figure it out after looking at the services that were starting up. There is apparent a 'zvol' script, which was the culprit. It was loading some ZFS stuff before the 'zfs' script. Once I set the 'gnop' script to startup before the 'zvol' script, worked like a charm. My zpool status now shows that it's using the gnop devices. Yay!! >> >> On Sun, Sep 19, 2010 at 14:04, Boris Samorodov wrote: >> > On Sun, 19 Sep 2010 13:55:41 -0700 Aaron wrote: >> >> On Sun, Sep 19, 2010 at 13:27, Boris Samorodov wrote: >> >> > On Sun, 19 Sep 2010 12:40:52 -0700 Aaron wrote: >> >> > >> >> >> # PROVIDE: gnop >> >> > >> >> > What if you try "PROVIDE: disks" instead? >> > >> >> No good. I also tried the following in the gnop script: >> > >> >> # PROVIDE: gnop >> >> # REQUIRE: mountcritlocal >> >> # BEFORE: zfs >> > >> > /etc/rc.d/geli has this: >> > - >> > # PROVIDE: disks >> > # REQUIRE: initrandom >> > # KEYWORD: nojail >> > - >> > >> > Seems that that should work for you. If not I'm out of ideas >> > for now. >> > >> >> The services -r looks promising, but the dmesg is still the same :( >> >> =A0When I disable zfs auto-mount, and then run it manually after boot, >> >> it uses the .nop devices that were created correctly as it should. >> > >> >> EXCERPT services -r >> >> /etc/rc.d/mdconfig >> >> /etc/rc.d/mountcritlocal >> >> /etc/rc.d/gnop >> >> /etc/rc.d/zfs >> > >> > -- >> > WBR, Boris Samorodov (bsam) >> > Research Engineer, http://www.ipt.ru Telephone & Internet SP >> > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve >> > >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" >> > > / > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem running custom startup script at proper time
> From owner-freebsd-questi...@freebsd.org Sun Sep 19 16:37:49 2010 > From: Aaron > Date: Sun, 19 Sep 2010 14:39:08 -0700 > To: freebsd-questions@freebsd.org > Subject: Re: Problem running custom startup script at proper time > > Doh! Forgot to reply to the mailing list. > > > Nope, that didn't work either. Darn. Maybe I'll just have to modify > the /etc/rc.d/zfs script to run the for loop first :( How about just modifying the REQUIRE header on it to include 'gnop' the sequencer that selects the order to run rc.d things in sorts based on the REQUIRE/PROVIDES dependencies. > > On Sun, Sep 19, 2010 at 14:04, Boris Samorodov wrote: > > On Sun, 19 Sep 2010 13:55:41 -0700 Aaron wrote: > >> On Sun, Sep 19, 2010 at 13:27, Boris Samorodov wrote: > >> > On Sun, 19 Sep 2010 12:40:52 -0700 Aaron wrote: > >> > > >> >> # PROVIDE: gnop > >> > > >> > What if you try "PROVIDE: disks" instead? > > > >> No good. I also tried the following in the gnop script: > > > >> # PROVIDE: gnop > >> # REQUIRE: mountcritlocal > >> # BEFORE: zfs > > > > /etc/rc.d/geli has this: > > - > > # PROVIDE: disks > > # REQUIRE: initrandom > > # KEYWORD: nojail > > - > > > > Seems that that should work for you. If not I'm out of ideas > > for now. > > > >> The services -r looks promising, but the dmesg is still the same :( > >> =A0When I disable zfs auto-mount, and then run it manually after boot, > >> it uses the .nop devices that were created correctly as it should. > > > >> EXCERPT services -r > >> /etc/rc.d/mdconfig > >> /etc/rc.d/mountcritlocal > >> /etc/rc.d/gnop > >> /etc/rc.d/zfs > > > > -- > > WBR, Boris Samorodov (bsam) > > Research Engineer, http://www.ipt.ru Telephone & Internet SP > > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > / ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem running custom startup script at proper time
--On Sunday, September 19, 2010 2:39 PM -0700 Aaron wrote: Doh! Forgot to reply to the mailing list. Nope, that didn't work either. Darn. Maybe I'll just have to modify the /etc/rc.d/zfs script to run the for loop first :( Do you load zfs.ko in loader.conf? I have built a few NAS systems on NanoBSD and found that I had to wait loading zfs until I had go the cache file copied from backup storage as I am using the diskless setup. Could it be that you need to run your script before loading zfs.ko? Cheers, Göran On Sun, Sep 19, 2010 at 14:04, Boris Samorodov wrote: On Sun, 19 Sep 2010 13:55:41 -0700 Aaron wrote: On Sun, Sep 19, 2010 at 13:27, Boris Samorodov wrote: > On Sun, 19 Sep 2010 12:40:52 -0700 Aaron wrote: > >> # PROVIDE: gnop > > What if you try "PROVIDE: disks" instead? No good. I also tried the following in the gnop script: # PROVIDE: gnop # REQUIRE: mountcritlocal # BEFORE: zfs /etc/rc.d/geli has this: - # PROVIDE: disks # REQUIRE: initrandom # KEYWORD: nojail - Seems that that should work for you. If not I'm out of ideas for now. The services -r looks promising, but the dmesg is still the same :( When I disable zfs auto-mount, and then run it manually after boot, it uses the .nop devices that were created correctly as it should. EXCERPT services -r /etc/rc.d/mdconfig /etc/rc.d/mountcritlocal /etc/rc.d/gnop /etc/rc.d/zfs -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem running custom startup script at proper time
Doh! Forgot to reply to the mailing list. Nope, that didn't work either. Darn. Maybe I'll just have to modify the /etc/rc.d/zfs script to run the for loop first :( On Sun, Sep 19, 2010 at 14:04, Boris Samorodov wrote: > On Sun, 19 Sep 2010 13:55:41 -0700 Aaron wrote: >> On Sun, Sep 19, 2010 at 13:27, Boris Samorodov wrote: >> > On Sun, 19 Sep 2010 12:40:52 -0700 Aaron wrote: >> > >> >> # PROVIDE: gnop >> > >> > What if you try "PROVIDE: disks" instead? > >> No good. I also tried the following in the gnop script: > >> # PROVIDE: gnop >> # REQUIRE: mountcritlocal >> # BEFORE: zfs > > /etc/rc.d/geli has this: > - > # PROVIDE: disks > # REQUIRE: initrandom > # KEYWORD: nojail > - > > Seems that that should work for you. If not I'm out of ideas > for now. > >> The services -r looks promising, but the dmesg is still the same :( >> When I disable zfs auto-mount, and then run it manually after boot, >> it uses the .nop devices that were created correctly as it should. > >> EXCERPT services -r >> /etc/rc.d/mdconfig >> /etc/rc.d/mountcritlocal >> /etc/rc.d/gnop >> /etc/rc.d/zfs > > -- > WBR, Boris Samorodov (bsam) > Research Engineer, http://www.ipt.ru Telephone & Internet SP > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problem running custom startup script at proper time
On Sun, 19 Sep 2010 12:40:52 -0700 Aaron wrote: > # PROVIDE: gnop What if you try "PROVIDE: disks" instead? -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Problem running custom startup script at proper time
I'm having trouble getting a custom startup script to run at the
proper time. I'm having to use gnop with my new Western Digital
WD10EARS (1TB, 4K sector size) because it reports the standard 512
byte to the OS. I'm basing it on
http://www.cod3r.com/2010/06/zfs-on-western-digital-ears-drives/ which
also says that it needs to be run on each boot so that ZFS will use
the .nop devices. So, I've created a custom startup script to
automatically do this for me at the proper time (before zfs starts and
auto-mounts). I'm having trouble getting it to work properly though.
In services -r, it is listed before the zfs startup script, but in
dmesg the gnop messages come after the zfs startup messages. Below is
excerpts from services -r, dmesg, and the startup script in its
entirety.
EXCERPT FROM services -r
/etc/rc.d/hostid_save
/etc/rc.d/mdconfig
/etc/rc.d/mountcritlocal
/etc/rc.d/gnop
/etc/rc.d/zfs
/etc/rc.d/FILESYSTEMS
/etc/rc.d/var
/etc/rc.d/cleanvar
EXCERPT FROM dmesg
Trying to mount root from ufs:/dev/ad0s1a
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS filesystem version 3
ZFS storage pool version 14
GEOM_NOP: Device ad6.nop created.
GEOM_NOP: Device ad8.nop created.
GEOM_NOP: Device ad10.nop created.
GEOM_NOP: Device ad12.nop created.
STARTUP SCRIPT, /etc/rc.d/gnop
#!/bin/sh
#
# PROVIDE: gnop
# REQUIRE: mdconfig
. /etc/rc.subr
name="gnop"
start_cmd="gnop_start"
gnop_start()
{
for i in ad6 ad8 ad10 ad12; do gnop create -S 4096 $i; done
}
load_rc_config $name
run_rc_command "$1"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why network doesn't get initialized on system startup?
Thursday, 19 August 2010 at 9:08:21 -0700, Yuri said: > On 08/19/2010 03:10, Glen Barber wrote: > >Are you loading the ndis(4) kernel module at boot via loader.conf? > > > > Yes, all ndis-related drivers (ndis.ko, if_ndis.ko and actual ndis > driver converted from windows one) are loaded from loader.conf. > When system comes up ndis0 is fully functional and I can initialize it > by hand fine. It just doesn't happen on startup. I can't remember where I saw this, but when you're using ndis you need to use SYNCDHCP instead of DHCP in ifconfig/rc.conf. Works for me no problem with a broadcom chip using ndis. Regards, Peter Harrison. > > Yuri > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why network doesn't get initialized on system startup?
On 08/19/2010 03:10, Glen Barber wrote: Are you loading the ndis(4) kernel module at boot via loader.conf? Yes, all ndis-related drivers (ndis.ko, if_ndis.ko and actual ndis driver converted from windows one) are loaded from loader.conf. When system comes up ndis0 is fully functional and I can initialize it by hand fine. It just doesn't happen on startup. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why network doesn't get initialized on system startup?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/19/10 2:00 AM, Yuri wrote: > On another rc.conf has: > wlans_ndis0=wlan0 > ifconfig_wlan0="ssid wifi-net-id weptxkey 1 deftxkey 1 wepmode on wepkey > 0x1234567890 DHCP" > and this one doesn't get initialized at startup. Are you loading the ndis(4) kernel module at boot via loader.conf? - -- Glen Barber -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) iQEcBAEBAgAGBQJMbQL5AAoJEFJPDDeguUajLbMH/Atp8JcOOsKcwGGs2rujobIC xjZuOQGAtAr7pisuFiDvqiax4zyDLg8xiiSFQxYKjGNJIxdp2ltl96/rvBakrhfp gKegUBO6RG+QQIHLE8IDkcxzx+xLxOYBkVIzhlofDlPtgZqc9EzKq7ipbnG5mW4H TtkpuZtX+AWWyBYf3DxNgndfHYETTKXDYDvt1ELyFnAZta0e7mYH4FkUb0/j/4sp hpk408HwUR5VCFNL6OP9NW9aAemxLy5KHWJ8NSl/HgNktEcyIYCHAwUno1/QPHFi EHXaaqGOBr+EPyBIRyDM533t1HH9ztDoDnLrblBYre4LMs+lO4X7zPThAgAs4iM= =oL1E -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Why network doesn't get initialized on system startup?
I have two similar machines, on one rc.conf has: wlans_ath0=wlan0 ifconfig_wlan0="ssid wifi-net-id weptxkey 1 deftxkey 1 wepmode on wepkey 0x1234567890 DHCP" and it gets initialized at startup. On another rc.conf has: wlans_ndis0=wlan0 ifconfig_wlan0="ssid wifi-net-id weptxkey 1 deftxkey 1 wepmode on wepkey 0x1234567890 DHCP" and this one doesn't get initialized at startup. The only difference is that the second one uses ndis0 with some preloaded ndis driver. It shouldn't matter. How can I make an interface to get initialized at startup and why it doesn't do this by itself? Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ipfw+natd startup order fixing
Hi there, a few months ago I inquired about an issue where using ipfw+natd worked on 8.0 but produced errors in 8.1. After searching the bugs database, I found multiple reports about it - http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/148137 and http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/148928. Both suggest manually loading ipdivert as a workaround, and fixing the rc scripts as solution. The offending changeset is http://svn.freebsd.org/viewvc/base/stable/8/etc/rc.d/ipfw?r1=196045&r2=203962, where natd was changed to be run as a post-cmd instead of a pre-cmd. According to svn, this defect has not been addressed in HEAD yet. I've tried modifying the rc scripts, so that natd becomes a dependency of ipfw - which ought to make it start. However, the rc script is marked as KEYWORD: nostart, which excludes it from the normal startup process and from the listing of 'services -r' (finally noticed this). So an alternative way to fix this would to make natd a standalone script, add a rc dependency, and remove the 'firewall_coscript' juggling in ipfw's rc script. What's the best way to get this problem fixed in svn? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
linux-nvu freezes upon startup
FreeBSD 8.1-PRERELEASE / amd64 Using KDE (latest port version) I have removed and reinstalled linux-nvu twice; however, it will not run. It hangs with its start up screen after clicking on any available option. Using 'gdb' I got this info: warning: no shared library support for this OS / ABI /usr/local/lib/linux-nvu/nvu-bin: error while loading shared libraries: libmozjs.so: cannot open shared object file: No such file or directory I did locate the library: $ locate libmozjs.so /usr/local/lib/firefox3/libmozjs.so /usr/local/lib/firefox3/sdk/lib/libmozjs.so /usr/local/lib/linux-nvu/libmozjs.so Has anyone else experienced a similar problem or have a solution? -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Last yeer I kudn't spel Engineer. Now I are won. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: Gnome startup awfully slow (7.3, gnome2.30)
I also have a similar problem (slow start-up) with gnome 2.30. In my case gnome-panel stops for some time (30 secs ?) then outputs a message to the console and then everything is ready to accept input. I can't attach the output message now. In my /etc/rc.conf I just added hald_enable="YES" dbus_enable="YES" and then created '.xinitrc' in ~ with the following line exec gnome-session I start everything with 'startx'. This way I can see error messages on the tty, where 'startx' has been launched. I can not say where debug messages are sent once you also enable gdm. d > Date: Thu, 10 Jun 2010 08:14:18 -0400 > From: m.e.sanlit...@gmail.com > To: a...@jenisch.at > CC: freebsd-questions@freebsd.org > Subject: Re: Gnome startup awfully slow (7.3, gnome2.30) > > On Thu, Jun 10, 2010 at 7:18 AM, Ewald Jenisch wrote: > > > Hi, > > > > On my system (FreeBSD 7.3 AMD64, system & kernel current as per today) > > it takes awully long to start up gnome (2.30) - "awfully long" meaning > > 2-3 minutes (this is on a Intel quadcore-CPU with 4GB RAM!) > > > > In my /etc/rc.conf I've got > > > > gnome_enable="YES" > > > > I've already ruled out the usual suspect being a missing/wrong entry > > in /etc/hosts (http://www.freebsd.org/gnome/docs/faq2.html#q20); my > > hostname ist resolvable including reverse-resolution, plus I've got > > the entries in my /etc/hosts. > > > > Is there any way to speed up gnome startup - or at least a pointer as > > to where I can start looking for the cause of the problem? > > > > Thanks in advance for any clue, > > -ewald > > > > > One possibility may be that X system is trying to auto-detect your hardware > which is taking time . > Checking X configuration files and making them conforming to your hardware > may eliminate this possibility . > > Thank you very much . > > Mehmet Erol Sanliturk > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" _ Hotmail: Powerful Free email with security by Microsoft. https://signup.live.com/signup.aspx?id=60969___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Gnome startup awfully slow (7.3, gnome2.30)
On Thu, Jun 10, 2010 at 7:18 AM, Ewald Jenisch wrote: > Hi, > > On my system (FreeBSD 7.3 AMD64, system & kernel current as per today) > it takes awully long to start up gnome (2.30) - "awfully long" meaning > 2-3 minutes (this is on a Intel quadcore-CPU with 4GB RAM!) > > In my /etc/rc.conf I've got > > gnome_enable="YES" > > I've already ruled out the usual suspect being a missing/wrong entry > in /etc/hosts (http://www.freebsd.org/gnome/docs/faq2.html#q20); my > hostname ist resolvable including reverse-resolution, plus I've got > the entries in my /etc/hosts. > > Is there any way to speed up gnome startup - or at least a pointer as > to where I can start looking for the cause of the problem? > > Thanks in advance for any clue, > -ewald > One possibility may be that X system is trying to auto-detect your hardware which is taking time . Checking X configuration files and making them conforming to your hardware may eliminate this possibility . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Gnome startup awfully slow (7.3, gnome2.30)
Hi, On my system (FreeBSD 7.3 AMD64, system & kernel current as per today) it takes awully long to start up gnome (2.30) - "awfully long" meaning 2-3 minutes (this is on a Intel quadcore-CPU with 4GB RAM!) In my /etc/rc.conf I've got gnome_enable="YES" I've already ruled out the usual suspect being a missing/wrong entry in /etc/hosts (http://www.freebsd.org/gnome/docs/faq2.html#q20); my hostname ist resolvable including reverse-resolution, plus I've got the entries in my /etc/hosts. Is there any way to speed up gnome startup - or at least a pointer as to where I can start looking for the cause of the problem? Thanks in advance for any clue, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Postfix bad command startup??
On 31/05/2010 22:07, Tim Judd wrote: On 5/31/10, Kaya Saman wrote: Hi, similar like I wrote before, to do with my migration from Solaris 9 to FreeBSD 8.0 x64 RELEASE. Postfix is being run in a BSD Jail and so far I have disabled as much as I could of sendmail which I did this to rc.conf within the jail: postfix_enable="YES" sendmail_enable="NONE" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" However upon startup Postfix gives me this problem: May 31 18:03:18 relay postfix/master[4280]: warning: /usr/local/libexec/postfix/smtpd: bad command startup -- throttling May 31 18:04:18 relay postfix/smtpd[4606]: fatal: open database /etc/aliases.db: No such file or directory May 31 18:04:19 relay postfix/master[4280]: warning: process /usr/local/libexec/postfix/smtpd pid 4606 exit status 1 May 31 18:04:19 relay postfix/master[4280]: warning: /usr/local/libexec/postfix/smtpd: bad command startup -- throttling May 31 18:05:19 relay postfix/smtpd[4629]: fatal: open database /etc/aliases.db: No such file or directory May 31 18:05:20 relay postfix/master[4280]: warning: process /usr/local/libexec/postfix/smtpd pid 4629 exit status 1 May 31 18:05:20 relay postfix/master[4280]: warning: /usr/local/libexec/postfix/smtpd: bad command startup -- throttling I can tell that it's listening as netstat -ap tcp reveals this: netstat: kvm not available: /dev/mem: No such file or directory Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 relay.smtp 110.52.7.217.2140 ESTABLISHED tcp4 0 0 relay.smtp web112111.mail.g.33920 ESTABLISHED tcp4 0 0 relay.smtp 110.52.6.29.4643 ESTABLISHED tcp4 0 0 relay.smtp 78-61-12-207.sta.28507 CLOSED tcp4 0 0 relay.smtp 78-61-12-207.sta.27646 CLOSE_WAIT tcp4 0 0 relay.smtp 78-61-12-207.sta.26479 CLOSE_WAIT tcp4 0 0 relay.smtp 110.52.6.35.2109 ESTABLISHED tcp4 0 0 relay.smtp 78-61-12-207.sta.23305 CLOSED tcp4 0 0 relay.smtp 78-61-12-207.sta.22314 CLOSE_WAIT tcp4 0 0 relay.smtp 78-61-12-207.sta.21323 CLOSE_WAIT tcp4 0 0 relay.ssh *.*LISTEN tcp4 0 0 relay.smtp *.*LISTEN /var/log/messages gives me this: May 31 18:10:24 relay postfix/smtpd[4662]: fatal: open database /etc/aliases.db: No such file or directory however I did run the command newaliases which did create the aliases file under /etc/mail/aliases with the aliases.db file being under there as well as under /etc. Currently no mail is being relayed throughout the domain so I can tell that it's not working as even the /var/log/maillog file is telling me that messages are queued but not sent if I use: mail -s test em...@address.com test ^D Can someone please help me work out what is causing Postfix to fail as I've managed to migrate my config from Linux to Solaris with not as many issues and problems as this so it really beats me... Many thanks, Kaya Kaya, You may need to edit the following alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases and run BOTH 'newaliases' and 'postalias /etc/aliases' depending on your setup. restart postfix for good measure if you telnet to your postfix IP and get the 220 banner, postfix is happy with the config and should work as config'd. if after establishing a telnet session, you don't get any banner, postfix is still having problems with something. start looking at logs again. Thanks so much Tim!!! :-) I hadn't used the 'postalias /etc/aliases' command at all so running it now actually made the system work pretty well.. At least I haven't restarted the Jail yet but so far everything works! I just hope this stays permanently as I find Jails a bit less stable then Solaris Zones which is what I'm trying to mimic with them; however, it might just be because I don't know how to use them yet as I've only just learned about how to create them and run simple services in them. Meaning that my statement is probably wy premature!! Now if I could just figure out how to start Squid through the rc.d scripts rather then running manually as root user as per my other posting that would be really cool... Best Regards, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Postfix bad command startup??
On 5/31/10, Kaya Saman wrote: > Hi, > > similar like I wrote before, to do with my migration from Solaris 9 to > FreeBSD 8.0 x64 RELEASE. > > Postfix is being run in a BSD Jail and so far I have disabled as much as > I could of sendmail which I did this to rc.conf within the jail: > > postfix_enable="YES" > sendmail_enable="NONE" > sendmail_submit_enable="NO" > sendmail_outbound_enable="NO" > sendmail_msp_queue_enable="NO" > > > However upon startup Postfix gives me this problem: > > May 31 18:03:18 relay postfix/master[4280]: warning: > /usr/local/libexec/postfix/smtpd: bad command startup -- throttling > May 31 18:04:18 relay postfix/smtpd[4606]: fatal: open database > /etc/aliases.db: No such file or directory > May 31 18:04:19 relay postfix/master[4280]: warning: process > /usr/local/libexec/postfix/smtpd pid 4606 exit status 1 > May 31 18:04:19 relay postfix/master[4280]: warning: > /usr/local/libexec/postfix/smtpd: bad command startup -- throttling > May 31 18:05:19 relay postfix/smtpd[4629]: fatal: open database > /etc/aliases.db: No such file or directory > May 31 18:05:20 relay postfix/master[4280]: warning: process > /usr/local/libexec/postfix/smtpd pid 4629 exit status 1 > May 31 18:05:20 relay postfix/master[4280]: warning: > /usr/local/libexec/postfix/smtpd: bad command startup -- throttling > > > I can tell that it's listening as netstat -ap tcp reveals this: > > netstat: kvm not available: /dev/mem: No such file or directory > Active Internet connections (including servers) > Proto Recv-Q Send-Q Local Address Foreign Address (state) > tcp4 0 0 relay.smtp 110.52.7.217.2140 > ESTABLISHED > tcp4 0 0 relay.smtp web112111.mail.g.33920 > ESTABLISHED > tcp4 0 0 relay.smtp 110.52.6.29.4643 > ESTABLISHED > tcp4 0 0 relay.smtp 78-61-12-207.sta.28507 CLOSED > tcp4 0 0 relay.smtp 78-61-12-207.sta.27646 CLOSE_WAIT > tcp4 0 0 relay.smtp 78-61-12-207.sta.26479 CLOSE_WAIT > tcp4 0 0 relay.smtp 110.52.6.35.2109 > ESTABLISHED > tcp4 0 0 relay.smtp 78-61-12-207.sta.23305 CLOSED > tcp4 0 0 relay.smtp 78-61-12-207.sta.22314 CLOSE_WAIT > tcp4 0 0 relay.smtp 78-61-12-207.sta.21323 CLOSE_WAIT > tcp4 0 0 relay.ssh *.*LISTEN > tcp4 0 0 relay.smtp *.*LISTEN > > > /var/log/messages gives me this: > > May 31 18:10:24 relay postfix/smtpd[4662]: fatal: open database > /etc/aliases.db: No such file or directory > > however I did run the command newaliases which did create the aliases > file under /etc/mail/aliases with the aliases.db file being under there > as well as under /etc. > > Currently no mail is being relayed throughout the domain so I can tell > that it's not working as even the /var/log/maillog file is telling me > that messages are queued but not sent if I use: > > mail -s test em...@address.com > > test > > ^D > > Can someone please help me work out what is causing Postfix to fail as > I've managed to migrate my config from Linux to Solaris with not as many > issues and problems as this so it really beats me... > > Many thanks, > > > Kaya Kaya, You may need to edit the following alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases and run BOTH 'newaliases' and 'postalias /etc/aliases' depending on your setup. restart postfix for good measure if you telnet to your postfix IP and get the 220 banner, postfix is happy with the config and should work as config'd. if after establishing a telnet session, you don't get any banner, postfix is still having problems with something. start looking at logs again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Postfix bad command startup??
Hi, similar like I wrote before, to do with my migration from Solaris 9 to FreeBSD 8.0 x64 RELEASE. Postfix is being run in a BSD Jail and so far I have disabled as much as I could of sendmail which I did this to rc.conf within the jail: postfix_enable="YES" sendmail_enable="NONE" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" However upon startup Postfix gives me this problem: May 31 18:03:18 relay postfix/master[4280]: warning: /usr/local/libexec/postfix/smtpd: bad command startup -- throttling May 31 18:04:18 relay postfix/smtpd[4606]: fatal: open database /etc/aliases.db: No such file or directory May 31 18:04:19 relay postfix/master[4280]: warning: process /usr/local/libexec/postfix/smtpd pid 4606 exit status 1 May 31 18:04:19 relay postfix/master[4280]: warning: /usr/local/libexec/postfix/smtpd: bad command startup -- throttling May 31 18:05:19 relay postfix/smtpd[4629]: fatal: open database /etc/aliases.db: No such file or directory May 31 18:05:20 relay postfix/master[4280]: warning: process /usr/local/libexec/postfix/smtpd pid 4629 exit status 1 May 31 18:05:20 relay postfix/master[4280]: warning: /usr/local/libexec/postfix/smtpd: bad command startup -- throttling I can tell that it's listening as netstat -ap tcp reveals this: netstat: kvm not available: /dev/mem: No such file or directory Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp4 0 0 relay.smtp 110.52.7.217.2140 ESTABLISHED tcp4 0 0 relay.smtp web112111.mail.g.33920 ESTABLISHED tcp4 0 0 relay.smtp 110.52.6.29.4643 ESTABLISHED tcp4 0 0 relay.smtp 78-61-12-207.sta.28507 CLOSED tcp4 0 0 relay.smtp 78-61-12-207.sta.27646 CLOSE_WAIT tcp4 0 0 relay.smtp 78-61-12-207.sta.26479 CLOSE_WAIT tcp4 0 0 relay.smtp 110.52.6.35.2109 ESTABLISHED tcp4 0 0 relay.smtp 78-61-12-207.sta.23305 CLOSED tcp4 0 0 relay.smtp 78-61-12-207.sta.22314 CLOSE_WAIT tcp4 0 0 relay.smtp 78-61-12-207.sta.21323 CLOSE_WAIT tcp4 0 0 relay.ssh *.*LISTEN tcp4 0 0 relay.smtp *.*LISTEN /var/log/messages gives me this: May 31 18:10:24 relay postfix/smtpd[4662]: fatal: open database /etc/aliases.db: No such file or directory however I did run the command newaliases which did create the aliases file under /etc/mail/aliases with the aliases.db file being under there as well as under /etc. Currently no mail is being relayed throughout the domain so I can tell that it's not working as even the /var/log/maillog file is telling me that messages are queued but not sent if I use: mail -s test em...@address.com test ^D Can someone please help me work out what is causing Postfix to fail as I've managed to migrate my config from Linux to Solaris with not as many issues and problems as this so it really beats me... Many thanks, Kaya ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NanoBSD weird startup messages
> Did you maybe word-wrap a comment line in /etc/rc.conf so that "files" was > the first word on a new line? If that's not it, try setting RC_DEBUG=YES in > /etc/rc.conf and see if you can pinpoint which startup script is causing you > problems. > > -- > Dan Nelson > dnel...@allantgroup.com > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > Thanks a lot - I owe you a beer When I pasted the stuff for dhcp the following stuff slipped #dhcpd_includedir="" # directory with config- files to include so rc.conf tries to start files and this kills the child in the beast. What I'm left to cope with is troubleshoot why dhclient freezes on getting the dhcpd offer. Log attached. This behaviour has probably something to do with the stuff that I have not compiled needed NIS/libs and botched rc.conf. Clues welcome Thanks. Dimitar nanodhcpd.log Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: NanoBSD weird startup messages
In the last episode (May 26), Dimitar Vassilev said: > Hello, > I'm facing the following funky excepts when booting NanoBSD on console: > > files: not found > I'm running on Alix1d - details are on http://pastebin.com/WY7hu0fL > > I did truss and found that devd and some binaries are seeking for a binary > called files in /usr/sbin/, /usr/games and /root/sbin. By default there > is no such binary and I'm wondering where did this get from. Did you maybe word-wrap a comment line in /etc/rc.conf so that "files" was the first word on a new line? If that's not it, try setting RC_DEBUG=YES in /etc/rc.conf and see if you can pinpoint which startup script is causing you problems. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
NanoBSD weird startup messages
Hello, I'm facing the following funky excepts when booting NanoBSD on console: files: not found I'm running on Alix1d - details are on http://pastebin.com/WY7hu0fL I did truss and found that devd and some binaries are seeking for a binary called files in /usr/sbin/, /usr/games and /root/sbin. By default there is no such binary and I'm wondering where did this get from. Any clues are welcome. Best regards, Dimitar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipfw natd rules not loading on startup
Just a sidenote:
On Sat, 15 May 2010 02:33:10 +0200, umage wrote:
> However, if I
> run the script manually, or call it from the end of /etc/rc, it will add
> these rules as well. Currently I am using a workaround.
It's not a good idea to modify /etc/rc. In your case, using the
mechanism s of /etc/rc(.shutdown).local is a good way to call
scripts that do not fit the rc.d concept. See "man rc.local"
for details.
So I would suggest something for /etc/rc.local like this:
#!/bin/sh
if [ -z "${source_rc_confs_defined}" ]; then
if [ -r /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
source_rc_confs
elif [ -r /etc/rc.conf ]; then
. /etc/rc.conf
elif [ -r /etc/rc.conf.local ]; then
. /etc/rc.conf.local
fi
fi
echo -n " custom-firewall"
/your/firewall/script.sh --here
The final dot + newline in the messages will be added by rc,
if I remember correctly.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipfw natd rules not loading on startup
On Sat, May 15, 2010 at 02:33:10AM +0200, umage wrote: > I performed a kernel+world update of my freebsd router, RELENG_8 branch, > apparently from the version 6 months ago to current. I use ipfw and a > shell script that gets loaded at startup. I noticed after rebooting that > ipfw did not load two rules, both of type "divert natd". However, if I > run the script manually, or call it from the end of /etc/rc, it will add > these rules as well. Currently I am using a workaround. Best to ask -STABLE. There's been some breakage of ipfw since end of April. I'm unsure as to whether they've all be resolved yet. Cheers. -- Jonathan Chen | To do is to be -- Nietzsche | To be is to do -- Sartre | Scooby do be do -- Scooby ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ipfw natd rules not loading on startup
I performed a kernel+world update of my freebsd router, RELENG_8 branch, apparently from the version 6 months ago to current. I use ipfw and a shell script that gets loaded at startup. I noticed after rebooting that ipfw did not load two rules, both of type "divert natd". However, if I run the script manually, or call it from the end of /etc/rc, it will add these rules as well. Currently I am using a workaround. I could not find any mention of warnings or errors in the logs. I couldn't find any way of making ipfw log errors. I tried piping my script's output to a file, but it did not say anything useful. Noone I asked knew what to do. I noticed that there has been a revamp of ipfw and its supporting scripts recently, so it's possible something broke along the way (for example, a missing rc dependency on natd?). Advice would be appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why doesn't this startup script run?
On Thu, 13 May 2010, Yuri Pankov wrote: > On Wed, May 12, 2010 at 04:20:12PM -0400, Andy Dills wrote: > > > > I'm working on integrating p0f with amavisd-new, and the command I need > > to run at startup is a little unwieldy: > > > > p0f -l 'tcp dst port 25' 2>&1 | /usr/local/bin/p0f-analyzer.pl 2345 & > > > > At first, I tried putting that in /etc/rc.local. No luck, don't know why > > it doesn't run. Ok, I tell myself, rc.local is a dinosaur anyway, take a > > second and make a simple rc.d script. > > > > So, I made /usr/local/etc/rc.d/p0fd containing: > > > > --- > > > > #!/bin/sh > > # > > Quoting rc(8): > Each script should contain rcorder(8) keywords, especially an appropriate > “PROVIDE” entry, and if necessary “REQUIRE” and “BEFORE” keywords. Thanks for the reply. I added this to the script (and renamed it p0f instead of p0fd): # PROVIDE: p0f # REQUIRE: LOGIN # BEFORE: securelevel # KEYWORD: shutdown It did not change the result, it still fails to start on boot, and still works if I call "/usr/local/etc/rc.d/p0f start" once I login to the box after it boots. Any other suggestions? I have to assume it has something to do with either the redirection of stdout and stderr to a script that is then backgrounded? If I do something that doesn't involve all of that, it starts fine on boot. How do I correct this? Earlier attempts went as far as to make a script to start the process, and then call the script from /etc/rc.local. I even tried doing a "/usr/local/etc/rc.d/p0f start" in /etc/rc.local. Nothing works until I go in and run the startup script by hand. Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Why doesn't this startup script run?
On Wed, May 12, 2010 at 04:20:12PM -0400, Andy Dills wrote:
>
> I'm working on integrating p0f with amavisd-new, and the command I need
> to run at startup is a little unwieldy:
>
> p0f -l 'tcp dst port 25' 2>&1 | /usr/local/bin/p0f-analyzer.pl 2345 &
>
> At first, I tried putting that in /etc/rc.local. No luck, don't know why
> it doesn't run. Ok, I tell myself, rc.local is a dinosaur anyway, take a
> second and make a simple rc.d script.
>
> So, I made /usr/local/etc/rc.d/p0fd containing:
>
> ---
>
> #!/bin/sh
> #
Quoting rc(8):
Each script should contain rcorder(8) keywords, especially an appropriate
“PROVIDE” entry, and if necessary “REQUIRE” and “BEFORE” keywords.
>
> . "/etc/rc.subr"
>
> name="p0f"
> rcvar=`set_rcvar`
>
> command="/usr/local/bin/p0f"
> command_args="-l 'tcp dst port 25' 2>&1 | /usr/local/bin/p0f-analyzer.pl 2345
> &"
> pidfile="/var/run/$name.pid"
>
> # read configuration and set defaults
> load_rc_config "$name"
> : ${p0f_enable="NO"}
>
> run_rc_command "$1"
>
> ---
>
> If I run "/usr/local/etc/rc.d/p0fd start" it fires right up. However, it
> still continues to refuse to run on boot.
>
> Any suggestions?
>
> (yes, it's executable, and yes I have p0f_enable="YES" in rc.conf)
>
> Thanks,
> Andy
>
> ---
> Andy Dills
> Xecunet, Inc.
> www.xecu.net
> 301-682-9972
> ---
Yuri
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Why doesn't this startup script run?
I'm working on integrating p0f with amavisd-new, and the command I need
to run at startup is a little unwieldy:
p0f -l 'tcp dst port 25' 2>&1 | /usr/local/bin/p0f-analyzer.pl 2345 &
At first, I tried putting that in /etc/rc.local. No luck, don't know why
it doesn't run. Ok, I tell myself, rc.local is a dinosaur anyway, take a
second and make a simple rc.d script.
So, I made /usr/local/etc/rc.d/p0fd containing:
---
#!/bin/sh
#
. "/etc/rc.subr"
name="p0f"
rcvar=`set_rcvar`
command="/usr/local/bin/p0f"
command_args="-l 'tcp dst port 25' 2>&1 | /usr/local/bin/p0f-analyzer.pl 2345 &"
pidfile="/var/run/$name.pid"
# read configuration and set defaults
load_rc_config "$name"
: ${p0f_enable="NO"}
run_rc_command "$1"
---
If I run "/usr/local/etc/rc.d/p0fd start" it fires right up. However, it
still continues to refuse to run on boot.
Any suggestions?
(yes, it's executable, and yes I have p0f_enable="YES" in rc.conf)
Thanks,
Andy
---
Andy Dills
Xecunet, Inc.
www.xecu.net
301-682-9972
---
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nfe0 startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/05/2010 01:15:13, Robert Jenssen wrote: > Many thanks to those who responded to my question. It seems that > waiting for the network to start up is a common problem. Recently > Jeremy Chadwick proprosed adding a /usr/local/etc/rc.d/waitnetwork > script. In response others have suggested the more radical step of > replacing /etc/rc.d with launchd. See Message-ID > <20100418213727.ga98...@icarus.home.lan> etc. I will await > developments. launchd(8) is a very interesting proposition, but it replaces a lot more than just the RC framework. It also covers cron(8), devd(8), inetd(8), init(8)/getty(8). Unlike RC scripts, launchd does /not/ expect the programs it manages to daemonise. In that respect, it's a lot more like daemontools or the sysV-ish inittab. While this has advantages (eg. in being able to restart crashed daemons promptly), it's a very different way of doing things, and there would have to be concomitant changes all over /usr/src. Not forgetting all of the available ported software. By my estimation, if FreeBSD were to commit to using launchd(8), the work required would absorb the majority of the available developer time running up to a major release. ie. if the decision was taken to go ahead, as soon as 9.0-RELEASE was branched, work on launchd in 10-CURRENT would have to start immediately, and take priority over many other development efforts in order to have the following 10.0-RELEASE up to the quality expected from the FreeBSD project. I don't think that's going to happen. I can see a launchd-esque system being introduced, but it would have to be radically rewritten compared to what MacOS X uses, offer compatibility shims for all of the systems it was intended to supplant, and it would take many years of gradual developent and change to get it to the desired state. In other words, keep up your RC script-writing skills for the foreseeable future. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvb6IYACgkQ8Mjk52CukIy8KwCglf3zwHd0G28UOUgHcUi0lSz4 eGgAni89VMuk6zknVBJRDcqzfPzHbkfB =7+ik -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nfe0 startup
Hi, Many thanks to those who responded to my question. It seems that waiting for the network to start up is a common problem. Recently Jeremy Chadwick proprosed adding a /usr/local/etc/rc.d/waitnetwork script. In response others have suggested the more radical step of replacing /etc/rc.d with launchd. See Message-ID <20100418213727.ga98...@icarus.home.lan> etc. I will await developments. Cheers, Rob Jenssen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nfe0 startup
On Thu, Apr 29, 2010 at 8:23 AM, Robert Jenssen < robertjens...@ozemail.com.au> wrote: > Hi, > > I am using a mother board with a NVIDIA MCP9 network chip on an AMD64 > motherboard. Here is the output of dmesg: > > > > Also the nfs mounts are now OK. > > It seems that nfe0 takes a while to get started. I am lucky that ntpdate is > called and delays things for long enough to allow nfe0 to startup. Without a > failing call to ntpdate the subsequent nfs mount fails and I get the > single-user prompt. > > Is there a better way than relying on ntpdate failing? > What does rc.conf have to say about nfe0? -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
nfe0 startup
empt to query device size failed: NOT READY, Medium not present - tray closed Root mount waiting for: usbus1 Trying to mount root from ufs:/dev/ad4s1a ugen0.2: at usbus0 ums0: on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 ugen0.3: at usbus0 ukbd0: on usbus0 kbd2 at ukbd0 nfe0: link state changed to UP During bootup I see the following messages (sanitised): nfe0: link state changed to DOWN Starting Network: lo0 nfe0. lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 nd6 options=3 nfe0: flags=8843 metric 0 mtu 1500 options=8010b ether inet w.x.y.z netmask 0xff00 broadcast w.x.y.z media: Ethernet autoselect (none) status: no carrier Starting devd. Starting ums0 moused. Configuring keyboard: keymap. Starting routed. Mounting NFS file systems:mount_nfs: ++: hostname nor servname provided, or not known mount_nfs: &&&&&&& : hostname nor servname provided, or not known . ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/g cc44 /usr/local/lib/qt4 a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout Creating and/or trimming log files. Starting syslogd. Additional ABI support: linux. Setting date via ntp. 29 Apr 11:03:25 ntpdate[869]: sendto(w.x.y.z): Unknown error: 0 29 Apr 11:03:25 ntpdate[869]: sendto(w.x.y.z): No route to host 29 Apr 11:03:26 ntpdate[869]: sendto(w.x.y.z): No route to host 29 Apr 11:03:26 ntpdate[869]: sendto(w.x.y.z): No route to host 29 Apr 11:03:27 ntpdate[869]: sendto(w.x.y.z): No route to host 29 Apr 11:03:27 ntpdate[869]: sendto(w.x.y.z): No route to host 29 Apr 11:03:29 ntpdate[869]: no server suitable for synchronization found Starting rpcbind. NFS access cache time=60 /etc/rc: WARNING: NIS domainname(1) is not set. /etc/rc: WARNING: failed precmd routine for ypbind Clearing /tmp (X related). Starting statd. Starting lockd. Updating motd:. Mounting late file systems:. Starting ntpd. Starting dbus. Starting hald. Configuring syscons: keymap blanktime. Starting sshd. Starting cron. Local package initialization: rtc. Starting background file system checks in 60 seconds. After login ifconfig shows that nfe0 is now active: ifconfig nfe0 nfe0: flags=8843 metric 0 mtu 1500 options=8010b ether inet w.x.y.z netmask 0xff00 broadcast w.x.y.z media: Ethernet autoselect (1000baseT ) status: active Also the nfs mounts are now OK. It seems that nfe0 takes a while to get started. I am lucky that ntpdate is called and delays things for long enough to allow nfe0 to startup. Without a failing call to ntpdate the subsequent nfs mount fails and I get the single-user prompt. Is there a better way than relying on ntpdate failing? Thanks in advance Rob Jenssen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nvidia module startup (solved)
Found the problem, a format error in my device.hints. Thanks all for the replies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nvidia module startup
On 04/28/10 10:55, Alexander Best wrote: you might want to try `nextboot -o '-v' -k kernel` to enable verbose booting during the next boot. maybe this will reveal your problem. I did not notice anything. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nvidia module startup
On Wed, 28 Apr 2010 16:43:35 -0400 sean wrote: > On 04/28/10 13:31, Alexandre L. wrote: > > Have you added the following line to /etc/rc.conf ? > > linux_enable="YES" > > > > Yes, it is. rc.conf isn't relevant because your problem occur long before rc.conf is read. Try putting: linux_load="YES" in loader.conf, or alternately rebuild the driver without linux support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re : nvidia module startup
On 04/28/10 13:31, Alexandre L. wrote: Have you added the following line to /etc/rc.conf ? linux_enable="YES" Yes, it is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re : nvidia module startup
Have you added the following line to /etc/rc.conf ? linux_enable="YES" --- En date de : Mer 28.4.10, sean a écrit : > De: sean > Objet: nvidia module startup > À: "Free BSD Questions list" > Date: Mercredi 28 avril 2010, 12h36 > Hello All, > > Setting up a new system here and the > nvidia module will not load on system startup. > > In the /boot/loader.conf I have placed nvidia_load="YES" as > I found in the instructions, but still no good. > > After a system start-up I have to manually load up nvidia > using kldloader. Once that is done X starts without > problems. > > Thanks in advance, > Sean > ___ > freebsd-questions@freebsd.org > mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nvidia module startup
you might want to try `nextboot -o '-v' -k kernel` to enable verbose booting during the next boot. maybe this will reveal your problem. also be sure to check out the freebsd section of the nvidia forum [1] to see if somebody reported a similar issue. [1] http://www.nvnews.net/vbulletin/forumdisplay.php?f=47 -- Alexander Best ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
