Telnet Secure login SRA?
I've just reset my telnet setup, now it comes up with a SRA secure login prompt, how can I get rid of it. I'm just using it for a short while to troubleshoot another installation, Qmail. telnet localhost Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Trying SRA secure login: User (UserName): Then if I do telnet local host 25 ==> telnet localhost 25 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection reset by peer telnet: Unable to connect to remote host Don't know if the SRA prompt is impeding the connection to the port -- View this message in context: http://old.nabble.com/Telnet-Secure-login-SRA--tp29518731p29518731.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: Telnet => servname ai_socktype error
TY Dan, I ran the tcpdump on the lo0 interface, ran telnet as shown below, interestingly only the "telnet localhost 25" produced an output (which I cannot fully decipher, except for the acknowledgment "hand shake" and the checksum, but can't figure out the "drop" or closure event Oddly, "telnet localhost smtp" and "telnet localhost " produced nothing in the dumpfile, just the "localhost: servname not supported for ai_socktype" to stdout [1] mach# telnet localhost > localhost: servname not supported for ai_socktype > [2] mach# telnet localhost smtp > localhost: servname not supported for ai_socktype > [3] mach# telnet localhost 25 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > Connection closed by foreign host. > Only [3] produced a tcpdump output, shown as follows ==> > mach# tcpdump -i lo0 -vvv >> tcpdumpfile > > Ctrl C > 7 packets captured > 7 packets received by filter > 0 packets dropped by kernel > 20:31:41.366749 IP (tos 0x10, ttl 64, id 11415, offset 0, flags [DF], proto TCP (6), length 60) localhost.54336 > localhost.25: S, cksum 0x5c3a (correct), 1583394158:1583394158(0) win 65535 20:31:41.366815 IP (tos 0x0, ttl 64, id 11416, offset 0, flags [DF], proto TCP (6), length 60) localhost.25 > localhost.54336: S, cksum 0xc615 (correct), 2069694587:2069694587(0) ack 1583394159 win 65535 20:31:41.366836 IP (tos 0x10, ttl 64, id 11417, offset 0, flags [DF], proto TCP (6), length 52) localhost.54336 > localhost.25: ., cksum 0x0c01 (correct), 1:1(0) ack 1 win 8960 20:31:41.398688 IP (tos 0x0, ttl 64, id 11421, offset 0, flags [DF], proto TCP (6), length 52) localhost.25 > localhost.54336: F, cksum 0x0be1 (correct), 1:1(0) ack 1 win 8960 20:31:41.398731 IP (tos 0x10, ttl 64, id 11422, offset 0, flags [DF], proto TCP (6), length 52) localhost.54336 > localhost.25: ., cksum 0x0bc2 (correct), 1:1(0) ack 2 win 8960 20:31:41.399162 IP (tos 0x10, ttl 64, id 11423, offset 0, flags [DF], proto TCP (6), length 52) localhost.54336 > localhost.25: F, cksum 0x0bc0 (correct), 1:1(0) ack 2 win 8960 20:31:41.399191 IP (tos 0x0, ttl 64, id 11424, offset 0, flags [DF], proto TCP (6), length 52) localhost.25 > localhost.54336: ., cksum 0x0bc0 (correct), 2:2(0) ack 2 win 8959 Hope you can see something in there, Thanks again PS: Couldn't find anything in the /var/log files either Shouldn't the telnet localhost generate a connection? -- Dan Nelson wrote: > > In the last episode (Aug 12), jaymax said: >> >> FreeBSD my.domain.com 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 >> 08:49:13 >> UTC 2009 >> r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >> >> Testing a Qmail SMTP installation with Telnet >> >> (normally use SSH for networking) >> >> Temporary Telnet set up for testing ==> >> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ >> >> Server set up ==> >> >> % telnet localhost 25 >> Trying 127.0.0.1... >> telnet: connect to address 127.0.0.1: Connection reset by peer > > That sounds like you connected but qmail crashed or otherwise uncleanly > closed the socket. Does a tcpdump on lo0 show any interesting activity > when > you try that command? > > -- > 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" > > -- View this message in context: http://old.nabble.com/Telnet-%3D%3E-servname-ai_socktype-error-tp29425269p29434929.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: Telnet => servname ai_socktype error
telnet 0 smtp is the same as telnet localhost 25 or telnet localhost smtp Ashish SHUKLA-6 wrote: > > jaymax writes: > > [...] > > >> % telnet 0 smtp >> 0: servname not supported for ai_socktype > > What according to you 0 is ? > > -- > Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F > A4B0 > freebsd.org!ashish | http://people.freebsd.org/~ashish/ > > “There was truth and there was untruth, and if you clung to the truth > even against the whole world, you were not mad.” (George Orwell, > "Nineteen Eighty-Four", 1949) > > > -- View this message in context: http://old.nabble.com/Telnet-%3D%3E-servname-ai_socktype-error-tp29425269p29431829.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"
Telnet => servname ai_socktype error
FreeBSD my.domain.com 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Testing a Qmail SMTP installation with Telnet (normally use SSH for networking) Temporary Telnet set up for testing ==> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Server set up ==> % cat /etc/services | grep telnet telnet 23/tcp telnet 23/udp % cat /etc/services | grep smtp smtp 25/tcpmail #Simple Mail Transfer smtp 25/udpmail #Simple Mail Transfer % cat /etc/rc.conf inetd_enable="YES" _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ But % telnet 0 smtp 0: servname not supported for ai_socktype % telnet localhost 25 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection reset by peer Trying ::1... telnet: connect to address ::1: Connection refused telnet: Unable to connect to remote host sockstat -4 ==> sockstat -4 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS myname sshd 1732 3 tcp4 nnn.xxx.yyy.zzz:22 aaa.bbb.ccc.ddd:1256 root sshd 1709 3 tcp4 nnn.xxx.yyy.zzz:22 aaa.bbb.ccc.ddd:1256 root gnome-sess 1529 10 tcp4 *:54384 *:* www httpd 1328 3 tcp4 nnn.xxx.yyy.zzz:80 *:* www httpd 1328 4 tcp4 nnn.xxx.yyy.zzz:443 *:* www httpd 1327 3 tcp4 nnn.xxx.yyy.zzz:80 *:* www httpd 1327 4 tcp4 nnn.xxx.yyy.zzz:443 *:* www httpd 1326 3 tcp4 nnn.xxx.yyy.zzz:80 *:* www httpd 1326 4 tcp4 nnn.xxx.yyy.zzz:443 *:* www httpd 1325 3 tcp4 nnn.xxx.yyy.zzz:80 *:* www httpd 1325 4 tcp4 nnn.xxx.yyy.zzz:443 *:* www httpd 1324 3 tcp4 nnn.xxx.yyy.zzz:80 *:* www httpd 1324 4 tcp4 nnn.xxx.yyy.zzz:443 *:* root Xorg 1314 3 tcp4 *:6000*:* root inetd 1267 6 tcp4 *:143 *:* root sshd 1239 4 tcp4 *:22 *:* root httpd 1207 3 tcp4 nnn.xxx.yyy.zzz:80 *:* root httpd 1207 4 tcp4 nnn.xxx.yyy.zzz:443 *:* avahiavahi-daem 1176 15 udp4 *:5353*:* avahiavahi-daem 1176 16 udp4 *:60699 *:* mysqlmysqld 948 11 tcp4 *:3306*:* root perl5.8.9 794 5 tcp4 *:1 *:* root perl5.8.9 794 6 udp4 *:1 *:* qmaild tcpserver 778 3 tcp4 *:25 *:* root tcpserver 776 3 tcp4 *:110 *:* root mountd 667 7 udp4 *:914 *:* root mountd 667 8 tcp4 *:914 *:* root syslogd580 7 udp4 *:514 *:* root ntpd 371 20 udp4 *:123 *:* root ntpd 371 22 udp4 nnn.xxx.yyy.zzz:123 *:* root ntpd 371 25 udp4 127.0.0.1:123 *:* Anyone having ahy ideas as to what may be amiss? Thanks! -- View this message in context: http://old.nabble.com/Telnet-%3D%3E-servname-ai_socktype-error-tp29425269p29425269.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"
resetting shmmax parameters
Hello, FreeBSD O/S 7.2 i386 1CPU AMD Server memory RAM memory hw.physmem: 1060540416 # sysctl -a | grep shm kern.ipc.shm_allow_removed: 0 kern.ipc.shm_use_phys: 0 kern.ipc.shmall: 8192 kern.ipc.shmseg: 128 kern.ipc.shmmni: 192 kern.ipc.shmmin: 1 kern.ipc.shmmax: 33554432 >From dmesg # grep memory /var/run/dmesg.boot real memory = 1073676288 (1023 MB) avail memory = 1036972032 (988 MB) # swapinfo Device 1K-blocks UsedAvail Capacity /dev/ad0s1b 1536000 32 1535968 0% /dev/ad1s1b 1048576 28 1048548 0% /dev/ad4s1b 2072576 44 2072532 0% Total 4657152 104 4657048 0% program suggested parameters for shared memory To reset the parameters: vi /etc/sysconfigtabin order to add the lines ipc: shm-max=2147483647 sem-mni=128 What is a safe / comfortable shmmax to use? Can I increase shmmax on the fly as in Linux or do I have to do reboot? Thanks! -- View this message in context: http://old.nabble.com/resetting-shmmax-parameters-tp27573158p27573158.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: Problem w/ mysql extension installation
A couple of hours later I return to this problem at the file is there and the extension installed "RATHER BIZARE" jaymax wrote: > > phpmyadmin requires the mysql extension which is apparently not included > in the mysql54 ports > > Installing it from > /usr/ports/databases/php5-mysql ==> > > > --- > --- > --- > In file included from > /usr/local/include/php/main/../main/php_config.h:2839, > from /usr/local/include/php/Zend/zend_config.h:1, > from /usr/local/include/php/Zend/zend.h:53, > from /usr/local/include/php/main/php.h:34, > from > /usr/ports/databases/php5-mysql/work/php-5.2.12/ext/mysql/php_mysql.c:32: > /usr/local/include/php/ext/php_config.h:1:30: error: ext/mysql/config.h: > No such file or directory > *** Error code 1 > 1 error > *** Error code 1 > > Stop in /usr/ports/databases/php5-mysql. > > > Indeed /usr/local/include/php/ext/mysql/config.h is not present! > > Should this have been installed with the mysql installation or from a > dependency? > > How can I correct this ? > > Thanks! > > > -- View this message in context: http://old.nabble.com/Problem-w--mysql-extension-installation-tp27184350p27187021.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"
Problem w/ mysql extension installation
phpmyadmin requires the mysql extension which is apparently not included in the mysql54 ports Installing it from /usr/ports/databases/php5-mysql ==> --- --- --- In file included from /usr/local/include/php/main/../main/php_config.h:2839, from /usr/local/include/php/Zend/zend_config.h:1, from /usr/local/include/php/Zend/zend.h:53, from /usr/local/include/php/main/php.h:34, from /usr/ports/databases/php5-mysql/work/php-5.2.12/ext/mysql/php_mysql.c:32: /usr/local/include/php/ext/php_config.h:1:30: error: ext/mysql/config.h: No such file or directory *** Error code 1 1 error *** Error code 1 Stop in /usr/ports/databases/php5-mysql. Indeed /usr/local/include/php/ext/mysql/config.h is not present! Should this have been installed with the mysql installation or from a dependency? How can I correct this ? Thanks! -- View this message in context: http://old.nabble.com/Problem-w--mysql-extension-installation-tp27184350p27184350.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: Catastrophic Installation Failure now!
The problem was caused by a permission change in the mysql data directory, in my case /disk02/db/mysql/DATA - why and how is beyond my comprehension. It would be a good tactic for developers to to include a troubleshooting script to check directory permissions in installations, as this is such a common problem. At a minimum a simple checklist would help. I have had situations where I have looked at files/directories after an installation and could not tell what it should be. Thanks again! jaymax wrote: > > MAJOR SCREWUP > > I was frustrated by a failure to create a ROOT password and decided to do > a clean reinstall > Did a "make deinstall" from the following ports > > -- View this message in context: http://old.nabble.com/Catastrophic-Installation-Failure-now%21-tp27100257p27126987.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"
Catastrophic Installation Failure now!
MAJOR SCREWUP I was frustrated by a failure to create a ROOT password and decided to do a clean reinstall Did a "make deinstall" from the following ports [i] /usr/ports/databases/mysql54-server [ii] /usr/ports/databases/mysql54-client [iii]/usr/ports/databases/mysql54-scripts Did a rm of the /etc/my.cnf file (There were no others in related or relevant areas) Also did a rm -rf of the database at /disk02/db/mysql/DATA Registered packages would be as follows:- # pkg_info | grep mysql bsdpan-DBD-mysql-4.013 DBD::mysql - MySQL driver for the Perl5 Database Interface php5-mysql-5.2.11_1 The mysql shared extension for php php5-mysqli-5.2.12 The mysqli shared extension for php qt4-mysql-plugin-4.4.3 Qt MySQL database plugin Reinstallation proceeded as follows: in /usr/ports/databases/mysql54-server ==> make 'pager=more' 'prompt=mysql54' 'socket=/usr/tmp/mysql.sock' 'localstatedir=/disk02/db/mysql/DATA' 'with_linuxthreads=yes' 'with_ssl=yes' install clean & in /usr/ports/databases/mysql54-scripts ==> make install clean mysql client apparently installed as a dependency by the server After compilation and installation Did the following: [i]/usr/local/bin/mysql_install_db then [ii] /usr/local/bin/mysqld_safe & first startup Stdout ==> [1] 37786 ax# 100110 07:05:36 mysqld_safe Logging to '/disk02/db/mysql/DATA/ax.lall.com.err'. 100110 07:05:37 mysqld_safe Starting mysqld daemon with databases from /disk02/db/mysql/DATA 100110 07:05:38 mysqld_safe mysqld from pid file /disk02/db/mysql/DATA/ax.lall.com.pid ended Now the err log from this is 100110 07:05:37 mysqld_safe Starting mysqld daemon with databases from /disk02/db/mysql/DATA 100110 7:05:37 [Note] Plugin 'FEDERATED' is disabled. /usr/local/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13) 100110 7:05:37 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. InnoDB: The InnoDB memory heap is disabled InnoDB: Neither mutexes nor rw_locks use GCC atomic builtins. InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 100110 7:05:37 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 100110 7:05:37 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 100110 7:05:37 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 100110 7:05:38 InnoDB Plugin 1.0.4 started; log sequence number 0 100110 7:05:38 [ERROR] /usr/local/libexec/mysqld: Can't find file: './mysql/host.frm' (errno: 13) 100110 7:05:38 [ERROR] Fatal error: Can't open and lock privilege tables: Can't find file: './mysql/host.frm' (errno: 13) 100110 07:05:38 mysqld_safe mysqld from pid file /disk02/db/mysql/DATA/ax.lall.com.pid ended repeating the command produced ==> 100110 07:12:01 mysqld_safe Starting mysqld daemon with databases from /disk02/db/mysql/DATA 100110 7:12:01 [Note] Plugin 'FEDERATED' is disabled. /usr/local/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13) 100110 7:12:01 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. InnoDB: The InnoDB memory heap is disabled InnoDB: Neither mutexes nor rw_locks use GCC atomic builtins. 100110 7:12:01 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 37356 100110 7:12:01 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 44244 100110 7:12:01 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 100110 7:12:02 InnoDB Plugin 1.0.4 started; log sequence number 44244 100110 7:12:02 [ERROR] /usr/local/libexec/mysqld: Can't find file: './mysql/host.frm' (errno: 13) 100110 7:12:02 [ERROR] Fatal error: Can't open and lock privilege tables: Can't find file: './mysql/host.frm' (errno: 13) 100110 07:12:02 mysqld_safe mysqld from pid file /disk02/db/mysql/DATA/ax.lall.com.pid ended RUNNING THE SUGGESTED UPGRADE AT "100110" ==> # /usr/local/bin/mysql_upgrade Looking for 'mysql' as: /usr/local/bin/mysql Looking for 'mysqlcheck' as: /usr/local/bin/m
Setting root password on mysql 5.4
Does anyone know how to set root password on a new mysql installation from the post? Can it be performed after starting the server with /usr/local/bin/mysqld_safe & Or for that matter with /usr/local/bin/mysql_secure_installation Thanks! -- View this message in context: http://old.nabble.com/Setting-root-password-on-mysql-5.4-tp27095130p27095130.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: mySQL 5.4 server & Post installation SNAFUs
OK Thanks again, still having problems with setting the root password. There is no my.cnf file Matthew Seaman-2 wrote: > > jaymax wrote: > >> Post installation SNAFUS >> > > >> [iv] /usr/local/bin/mysqladmin -u root password ==> >> ax# /usr/local/bin/mysqladmin -u root password '' >> /usr/local/bin/mysqladmin: connect to server at 'localhost' failed >> error: 'Access denied for user 'root'@'localhost' (using password: NO)' >> ax# /usr/local/bin/mysqladmin -u root -h ax.lall.com password >> /usr/local/bin/mysqladmin: connect to server at 'ax.lall.com' failed >> error: 'Access denied for user 'root'@'ax.lall.com' (using password: NO)' >> HOW can I setup root password ? > > If you're currently logged into ax.lall.com, then you definitely want > to use '-h localhost' (or nothing, as that's the default). If there is > already a root password, obviously you need to give it. Conversely, if > you've got a password set in /root/.my.cnf or some other my.cnf file but > this is a brand new mysql install with no root password yet, then you need > to temporarily move that file aside: mysql doesn't let you in if you try > and supply a password for a no-password account. > > I advise using mysql_secure_installation -- but you're still going to have > to move aside any pre-existing .my.cnf files. Also, as a general security > thing, preferably don't allow root logins to mysql from anywhere other > than > localhost. > > There was a v 6.2 install attempt but had to be rolled back. All files were removed 'hopefully'. Version 5.5 was downloaded to a src directory but not installed. A "find -f /* -name 'my.cnf' -print" search found nothing except copies in the src directory of v 5.5 and those in the ports. When the server is started with "/usr/local/bin/mysqld_safe &" I get the same responses as above re: setting the root password attempt > /usr/local/bin/mysqladmin -u root -h localhost password > /usr/local/bin/mysqladmin: connect to server at 'localhost' failed > error: 'Access denied for user 'root'@'localhost' (using password: NO)' > When I attempt with a "/usr/local/bin/mysql_secure_installation" start (after killing the mysql safe start) I get the following ==> > In order to log into MySQL to secure it, we'll need the current > password for the root user. If you've just installed MySQL, and > you haven't set the root password yet, the password will be blank, > so you should just press enter here. > > Enter current password for root (enter for none): > ERROR 2002 (HY000): Can't connect to local MySQL server through socket > '/tmp/mysql.sock' (2) > Enter current password for root (enter for none): > ERROR 2002 (HY000): Can't connect to local MySQL server through socket > '/tmp/mysql.sock' (2) > Enter current password for root (enter for none): > So I obviously have the wrong approach, please advise. Thanks! -- View this message in context: http://old.nabble.com/mySQL-5.4-server---Post-installation-SNAFUs-tp27086064p27089065.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"
mySQL 5.4 server & Post installation SNAFUs
Installed mysql-server54 from the ports
7.2-RELEASE FreeBSD 7.2-RELEASE #0: O/S running Apache/2.2.11 (FreeBSD)
installed PHP 5.2.12
configure options used ==>
make pager=more prompt=mysql54 socket=/usr/tmp/mysql.sock
localstatedir=/disk02/db/mysql/DATA with_linuxthreads=yes with_ssl=yes
install clean &
Final output ==> { ..?[n] ; problems, questions and answers sought }
ax# /usr/local/bin/mysql_install_db
Installing MySQL system tables...
091230 13:35:02 [ERROR] The update log is no longer supported by MySQL in
version 5.0 and above. It is replaced by the binary log.
091230 13:35:02 [Note] Falcon: unable to open system data files.
091230 13:35:02 [Note] Falcon: creating new system data files.
091230 13:35:03 [Warning] Forcing shutdown of 2 plugins
OK
Filling help tables...
091230 13:35:04 [ERROR] The update log is no longer supported by MySQL in
version 5.0 and above. It is replaced by the binary log.
091230 13:35:05 [Warning] Forcing shutdown of 2 plugins
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system ...?[i]
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/local/bin/mysqladmin -u root password 'new-password'
/usr/local/bin/mysqladmin -u root -h ax.lall.com password 'new-password'
Alternatively you can run:
/usr/local/bin/mysql_secure_installation...?[ii]
which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.
See the manual for more instructions.
You can start the MySQL daemon with:
cd /usr/local ; /usr/local/bin/mysqld_safe & ...?[iii]
You can test the MySQL daemon with mysql-test-run.pl
cd /usr/local/mysql-test ; perl mysql-test-run.pl
Please report any problems with the /usr/local/bin/mysqlbug script!
The latest information about MySQL is available at http://www.mysql.com/
Support MySQL by buying support/licenses from http://shop.mysql.com/
___
Post installation SNAFUS
[i] support-files/mysql.server are apparently in "/usr/local/share/mysql" am
I correct, all of them?
[ii] mysql_secure_installation is not found in this installation, it is in
v. 5.5 however.
[iii] Start restricted to /usr/local/bin/mysqld_safe & apparently since
mysql_secure_installation is not available
[iv] /usr/local/bin/mysqladmin -u root password ==>
ax# /usr/local/bin/mysqladmin -u root password ''
/usr/local/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost' (using password: NO)'
ax# /usr/local/bin/mysqladmin -u root -h ax.lall.com password
/usr/local/bin/mysqladmin: connect to server at 'ax.lall.com' failed
error: 'Access denied for user 'root'@'ax.lall.com' (using password: NO)'
HOW can I setup root password ?
--
View this message in context:
http://old.nabble.com/mySQL-5.4-server---Post-installation-SNAFUs-tp27086064p27086064.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: Possible mysql.sock problem | ERROR 2002 (HY000)
Thanks !!!
Got it resolved after adding
mysql_socket="/usr/tmp/mysql.sock" to the rc.conf file
Removing the /etc/my.cnf file as the aetting were redundant with those used
in the compilation
deinstalling and reinstalling both the server and the client
Matthew Seaman-2 wrote:
>
> jaymax wrote:
>
>> Direct start from script /usr/local/etc/rc.d/mysql-server start fails
>> also
>>
>> And running /usr/local/bin/mysql ==>
>> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
>> '/usr/tmp/mysql.sock' (2)
>>
>
> There's a $mysql_socket rc.conf variable you need to set as well.
>
>> Settings in rc.conf
>> mysql_enable="YES"
>> mysql_limits="YES"
>> mysql_dbdir="/disk02/db/mysql/DATA"
>> mysql_args=""
> mysql_socket="/usr/tmp/mysql.sock"
>
> (Although if /usr/tmp is set to mode 1777, what's the benefit of using
> that
> location rather than the default /tmp/mysql.sock ?)
>
> Initially they were on their own file systems both ran into problems of
> restricted sizes and overflow condition.
>
>
> Judging by the complaints about 'update log no longer supported' I'm
> guessing that there is somewhere a my.cnf or a .my.cnf file filled with
> configuration settings appropriate to a much earlier version of MySQL.
> A good strategy is to grab one of the sample .cnf files from
> /usr/local/share/mysql (according to the capabilities of your server)
> copy that into ${mysql_dbdir}/my.cnf and edit to make any local
> customizations.
>
> Aparently ignored after
>
--
View this message in context:
http://old.nabble.com/Possible-mysql.sock-problem-%7C-ERROR-2002-%28HY000%29-tp27001411p27066296.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"
Possible mysql.sock problem | ERROR 2002 (HY000)
HELP! NEEDED URGENTLY 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 installed /usr/ports/databases/mysql54-server from ports Installation seemed to go to completion - OK but # /usr/local/bin/mysql_install_db - ERRORS listed as ==> Installing MySQL system tables... 091230 13:35:02 [ERROR] The update log is no longer supported by MySQL in version 5.0 and above. It is replaced by the binary log. 091230 13:35:02 [Note] Falcon: unable to open system data files. 091230 13:35:02 [Note] Falcon: creating new system data files. 091230 13:35:03 [Warning] Forcing shutdown of 2 plugins OK Filling help tables... 091230 13:35:04 [ERROR] The update log is no longer supported by MySQL in version 5.0 and above. It is replaced by the binary log. 091230 13:35:05 [Warning] Forcing shutdown of 2 plugins OK Then running /usr/local/bin/mysqld_safe & ==> 091230 17:45:16 mysqld_safe Logging to '/disk02/db/mysql/DATA/ax.lall.com.err'. 091230 17:45:16 mysqld_safe Starting mysqld daemon with databases from /disk02/db/mysql/DATA 091230 17:45:16 mysqld_safe mysqld from pid file /disk02/db/mysql/DATA/ax.lall.com.pid ended Direct start from script /usr/local/etc/rc.d/mysql-server start fails also And running /usr/local/bin/mysql ==> ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/usr/tmp/mysql.sock' (2) Tried various strategies for mysql.sock problems as suggested in thre forum but can't seem to get any to work, if someone has any ideas they will be much appreciated. Thanks! PS: Settings in rc.conf mysql_enable="YES" mysql_limits="YES" mysql_dbdir="/disk02/db/mysql/DATA" mysql_args="" In my.cnf file [client] socket=/usr/tmp/mysql.sock [mysqld] socket=/usr/tmp/mysql.sock /usr/tmp permissions set to drwxrwxrwt datadir = mysql:mysql ownership HELP! NEEDED URGENTLY -- View this message in context: http://old.nabble.com/Possible-mysql.sock-problem-%7C-ERROR-2002-%28HY000%29-tp27001411p27001411.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: Restricting tar or pax to a single file system
I think my reply went to the previous post, but here is
The syntax here is confusing, should it be >
[ignoring other options]
tar -c -W one-file-system -f tarfile2Becreated.tar /
{
>From the man pages
-W longopt=value
Long options (preceded by --) are only supported directly on systems that
have the getopt_long(3) function. The -W option can be used to access long
options on systems that do not support this function.
}
Or is there another synopsis?
Thanks!
Dan Nelson wrote:
>
> In the last episode (Nov 21), jaymax said:
>> How does one restrict tar or fax to a single file system when tarring or
>> paxing from root (/) ?
>
> For tar:
>
> --one-file-system (-W one-file-system)
> (c, r, and u modes) Do not cross mount points.
>
> --
> 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"
>
>
--
View this message in context:
http://old.nabble.com/Restricting-tar-or-pax-to-a-single-file-system-tp26463168p26466083.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: Restricting tar or pax to a single file system
The syntax here is confusing, should it be >
[ignoring other options]
tar -c -W one-file-system -f tarfile2Becreated.tar /
{
>From the man pages
-W longopt=value
Long options (preceded by --) are only supported directly on systems that
have the getopt_long(3) function. The -W option can be used to access long
options on systems that do not support this function.
}
Or is there another synopsis?
Thanks!
jaymax wrote:
>
> How does one restrict tar or fax to a single file system when tarring or
> paxing from root (/) ?
>
> Thanks!
>
>
>
--
View this message in context:
http://old.nabble.com/Restricting-tar-or-pax-to-a-single-file-system-tp26463168p26465969.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"
Restricting tar or pax to a single file system
How does one restrict tar or fax to a single file system when tarring or paxing from root (/) ? Thanks! -- View this message in context: http://old.nabble.com/Restricting-tar-or-pax-to-a-single-file-system-tp26463168p26463168.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"
Disk label inconsistencies
I have a rather bizarre problem. I have been trying to upgrade forever w/ endless problems, but may have found the cause of some of the problems. Running O/S 6.0. My system disk is displayed in df etc as /dev/ad0 with slice & partitions as ad0s1a, ad0s1b, ad0s1e, .. , etc. It is similarly displayed under /dev. However, when I get to the disk label editor it shows up as ad0a, and slice & partitions as ad0as1a, ad0as1b, ad0as1e, .. , etc. I've tried changing these, even with the Fdisk editor but they seem to persist, perhaps when I restore the dump files. NOTE: ad0a or add0asx ... etc does not show up under /dev . Needless to say the following are standard messages from the upgrade attempts Error mounting /mnt/dev/ad0as1e on /mnt/tmp : Input/output error Error mounting /mnt/dev/ad0as1f on /mnt/usr : Input/output error Is there any solution to this short of reformatting the whole disk as new disk from scratch. Thanks! "Disk label inconsistencies" -- View this message in context: http://www.nabble.com/Disk-label-inconsistencies-tp25849056p25849056.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: Undelete or recover from badblocks on disks
Thanks again Roland, I think I must have lost those files when fsck_ffs did its salvage operation The expected files were /disk02/bkup/dump/ad0s1a-090909.dump /disk02/bkup/dump/ad0s1e-090909.dump /disk02/bkup/dump/ad0s1f-090909.dump fls from the image file => listfile # sed -n 30153,30158p list d/d 4804608:bkup d/d 918528: servers + d/d 918529: apache ++ d/d 918530: httpd-2.0.40 +++ d/d 918531: os d/d 918532:os2 Shows the bkup directory but no subdirectory (i.e ../dump/. or dumpfiles Now, if perchance these files were found with fls what would have been the method to extract them back and make them readable to the file system. Thanks _ Roland Smith wrote: > > On Fri, Sep 18, 2009 at 10:17:31PM -0700, jaymax wrote: >> >> Thanks Roland, > > Create a disk image from the damaged drive, and save it on another disk > with enough space. You can use dd(1) to create a disk image. You can > devide the image into several files. For example, I will use dd to get two > consecutive 10 > > # dd if=/dev/da0s1 of=dd1.img bs=1m count=10 > 10+0 records in > 10+0 records out > 10485760 bytes transferred in 1.031497 secs (10165575 bytes/sec) > > The (valid, IMHO) reason for using disk images is that you want to > investigate a copy of the data, so you cannot accidentily destroy the > original data. > -- View this message in context: http://www.nabble.com/Undelete-or-recover-from-badblocks-on-disks-tp25498179p25530662.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: Undelete or recover from badblocks on disks
Thanks Roland, smartctl showed disk to be fine! fls requires a disk image, is there one created by default in FreeBSD 6.0 . > SYNOPSIS >fls [-adDFlpruvV] [-m mnt ] [-z zone ] [-f fstype ] [-s seconds ] > [-i >imgtype ] [-o imgoffset ] image [images] [ inode ] > Running fls in directory of deleted files/dir produced > #fls -adr 2 > Missing image file names (img_open) > Is there a solution to this ? Roland Smith wrote: > > Check the disk with smartctl(8) from the sysutils/smartmontools port to > check > that this isn't a hardware malfunction. If it is a hardware malfunction, > the > disk is dying and should be replaced ASAP. > > If the hardware is OK, try fls from sysutils/sleuthkit. As long as the > data > isn't overwritten, it should still be there. > > Roland > -- View this message in context: http://www.nabble.com/Undelete-or-recover-from-badblocks-on-disks-tp25498179p25518685.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"
Undelete or recover from badblocks on disks
I seemed to have lost some critical dump files during a restore. The directory in which they were backed up in seemed to vaporize. The data was present as indicated by df -h but the directory was not listed. fsck on the disk was ineffective fsck_ffs produced an extensive listing of bad block, a final SALVAGE option, but on completion, the disk "capacity" from the df -h was significantly reduced. Is there anyway of recovering even 'partial' data from these lost blocks? The drive has been disconnected so that there would be no 'write' activities? Thanks -- View this message in context: http://www.nabble.com/Undelete-or-recover-from-badblocks-on-disks-tp25498179p25498179.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: Approx. restore time estimate
I was wondering if 24, 48, 72 hrs or even a lifetime was the order of time. I am now approaching 24 hrs. probably wait until my geriatric years and come back to look at the machine ... lol!!! Or would I have been better off using dd if=/dev/* of=output/path/filename [options] All other things being equal, would the removal of the "restore" overheads be significant relative to those from dd . Thanks Lars Eighner-2 wrote: > > On Mon, 14 Sep 2009, jaymax wrote: > >> >> Thanks! >> >> That might explain. Is there an alternate process you would recommend >> with >> at least equal reliability. > > I don't know of anything that isn't a bigger can of worms in a file system > of any complexity to speak of. > >> BTW I should have mentioned that I was restoring from a disk file rather >> than from a tape > > I was speaking of disk to disk. > > -- View this message in context: http://www.nabble.com/Approx.-restore-time-estimate-tp25443580p25457128.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: Approx. restore time estimate
Thanks! That might explain. Is there an alternate process you would recommend with at least equal reliability. BTW I should have mentioned that I was restoring from a disk file rather than from a tape Thanks again. --- Lars Eighner-2 wrote: > > On Mon, 14 Sep 2009, jaymax wrote: > > > I cannot begin to give you a number in the ballpark, all I can tell you is > that restore *is* very, very slow and lacks reassuring progress > indicators. > > -- > Lars Eighner > http://www.larseighner.com/index.html > 8800 N IH35 APT 1191 AUSTIN _ > > -- View this message in context: http://www.nabble.com/Approx.-restore-time-estimate-tp25443580p25445497.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"
Approx. restore time estimate
I do not expect an exact or precise answer here, given all the subjective & dependent parameters. Just a rough ballpark approximation, what time frame should a restore occur in? param :- an ~1Ghz system, running 6.x O/S, dumpfile ~ 30 Gb, UFS2 file systems w/ default blocksize, target directory 400 Gb w/ > 190 Gb free capacity, minimal use system booted from Fixit Just wanted to get an idea if I am going anywhere or workig fast being stuck somewhere or nowhere. Thanks -- View this message in context: http://www.nabble.com/Approx.-restore-time-estimate-tp25443580p25443580.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: Upgrading 6.0 to 6.x... without /var
Polytropon wrote: > > On Thu, 10 Sep 2009 14:14:55 -0700 (PDT), jaymax > wrote: >> =>> Error Messages >> [i] "Error mounting /mnt/dev ad0as1e on /mnt/usr : Input/output error" >> [ii] "Error mounting /mnt/dev ad0as1f on /mnt/usr : Input/output error" > ^^^ > This looks weird. Is this for real? Partition names should > be ad0s1e (or f), not ad0*a*s1e (or f). Have you specified > the correct device names? > > You are correct my typos, they are > ad0s1e and ad0s1f for /tmp and /usr respectively; /var is replaced by soft > link > ln -s /usr/var /var > ( running an email server on this box runs the risk of 'filesystem full' > with a 'small' restricted /var partition , this way the problem is escaped > ) > > >> Then tries to a form a holographic shell >> asks for directory to save current /etc?, prompts with /var/tmp/etc, I >> changed it to "/usr/tmp2/etc" => "Unable to backup your /etc int >> /usr/tmp2/etc. Do you want to continue anyway?" >> Opt'd out w/ a No! selection. >> >> Could this problem result from the absence of a /var partition ? > > No, but the system can neither access /var (even as a symlink), nor > can it access /usr because it isn't mounted - as far as it seems to > me. > > They are mounted > >> Is there an alt. Strategy for a 6.0 =>6.4 upgrade, while maintaining all >> the >> previous custom and configuration files? > > You could first start with a live system CD (FreeBSD's own one or > FreeSBIE), then mount / and /usr (where /var does exist) and copy > the important subtrees, such as /etc, /var/db/pkg and /usr/local/etc. > You can then overwrite everything and reinstall your configuration > files manually. > > I'll give that a try, I've already started on the cvsupd approach > suggested earlier. > > Thanks! > > > -- > 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" > > -- View this message in context: http://www.nabble.com/Upgrading-6.0-to-6.x...-without--var-tp25391151p25408257.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"
Upgrading 6.0 to 6.x... without /var
I have a 6.0 installation without a /var slice. Instead I have a soft link of /usr/var to a /var@ file. Now I am attempting an upgrade to 6.4 and getting an error condition. I am using Disk 1 of the 6.4 distro >> Upgrade [Upgrade an existing system] >> All [All system sources. binaries and X-Windows System] >> added Ports and mount points. System goes through its fsck-ffs -y routines on /mnt/dev/* devices. =>> Error Messages [i] "Error mounting /mnt/dev ad0as1e on /mnt/usr : Input/output error" [ii] "Error mounting /mnt/dev ad0as1f on /mnt/usr : Input/output error" Then tries to a form a holographic shell asks for directory to save current /etc?, prompts with /var/tmp/etc, I changed it to "/usr/tmp2/etc" => "Unable to backup your /etc int /usr/tmp2/etc. Do you want to continue anyway?" Opt'd out w/ a No! selection. Could this problem result from the absence of a /var partition ? Is there an alt. Strategy for a 6.0 =>6.4 upgrade, while maintaining all the previous custom and configuration files? -- View this message in context: http://www.nabble.com/Upgrading-6.0-to-6.x...-without--var-tp25391151p25391151.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: Inconsistency in root partition size
Mel Flynn-2 wrote: > > > This is exactly what I figured. Some files are hiding behind a mount > point. > The got there most likely, cause you did make installworld without /usr > mounted, which would happen if you have the FreeBSD source tree on a > different > location, reboot into single user mode, only mount the source tree and do > installworld. > > To repair, reboot into single user. Run the following commands: > fsck -y / > mount -u -o rw / > rm -rf /usr/* > exit > > This should delete the offending files. > Thanks, you have been a tremendous help That was precisely the problem and solution, the capacity from df-k is back down to 10% thanks again with your permission I'd like to post your advise on the FreeBSD Forum, of course with credits =) -- View this message in context: http://www.nabble.com/Inconsistency-in-root-partition-size-tp25314145p25356456.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: Inconsistency in root partition size
Mel Flynn-2 wrote: > > On Monday 07 September 2009 20:54:51 jaymax wrote: > > Did you do the du without anything mounted? Cause you have the df output > with > mounts. > If you can't find the missing space, then I suggest making a backup of / > with > dump(8), booting from livefs and restoring the dump. The dump should not > be in > the 390M range, rather in the 40-50M range. > Disconnected my drives, except for system root, then du is not found mach_1# whereis du > du: /usr/bin/du /usr/share/man/man1/du.1.gz /usr/src/usr.bin/du > could have done a 'umount' but results would have been the same, so I think. Did a backup (dump) of /, file produced in 400Mb range dump -0Lauf /disk03/dump/root2.dump /dev/ad0s1a dumpfile size > mach_1# ls -l /disk03/dump/root2.dump > -rw-r--r-- 1 root wheel 426956800 Sep 7 16:31 /disk03/dump/root2.dump > > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > /dev/ad0s1a5076304077545926687%/ > Compared with > du -xhc / > 44Mtotal > So I decided to do a listing of files in the dump > restore -tf /disk03/dump/root2.dump > rootrestore-0.lst > To my surprise rootrestore-0.lst contains a whole listings of ./usr/ files ex. > 2926 ./usr/include/bsnmp/snmpmod.h > 2927 ./usr/include/bsnmp/snmp_atm.h > Now /usr is on a separate and distinct partition > /dev/ad0s1f 36205990 25765232 754428077%/usr > Hope someone can make some sense of this. -- View this message in context: http://www.nabble.com/Inconsistency-in-root-partition-size-tp25314145p25338956.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: Inconsistency in root partition size
Mel Flynn-2 wrote: > > On Monday 07 September 2009 20:54:51 jaymax wrote: > Thanks, will do a new dump, one question - how can one determine that the dumpfile produced is good? -- View this message in context: http://www.nabble.com/Inconsistency-in-root-partition-size-tp25314145p25337689.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: Inconsistency in root partition size
Polytropon wrote: > > > You can of course read "man hier" to obtain information about > the file system hierarchy. In settings where partitions are > used to separate functional parts of the hierarchy, there's > often not much stuff that goes into /, because / is primarily > reserved for the basic system and the mountpoints; things > like /tmp, /var, /usr and /home go to different partitions. > > Check the content of /boot. Maybe you have more than one > kernel image and module files in there. You can as well use > > # du -sch / > > with only / mounted to get a first impression which subtrees > do occupy how much disk space. > > mach_1# df -k > Filesystem 1K-blocks UsedAvail Capacity Mounted on > /dev/ad0s1a5076304073845963687%/ > devfs 1 10 100%/dev > /dev/ad0s1e505646 14212 450984 3%/tmp > /dev/ad0s1f 36205990 25759138 755037477%/usr > /dev/ad1s1e 74696394 9836586 5888409814%/disk02 > /dev/ad4s1d 376405390 252115006 9417795473%/disk03 > devfs 1 10 100%/usr/var/named/dev > mach_1# cd / > mach_1# du -xhc > 2.0K./.snap > 2.0K./disk02 > 2.0K./disk03 > 2.0K./tmp > 2.0K./usr > 512B./dev > 2.0K./cdrom1 > 2.1M./stand > 3.1M./etc > 2.0K./cdrom > 902K./bin > 21M./boot > 3.2M./lib > 270K./libexec > 2.0K./mnt > 2.0K./proc > 2.0K./dist > 7.8M./root > 3.3M./sbin > 2.0K./.mozilla > 2.0K./net > 2.0K./WARD2V1 > 2.0K./ORIN > 2.0K./WARA > 2.0K./ORNUSR > 2.0K./WARD3V1 > 2.0K./ORND02 > 2.0K./WARUSR > 1.2M./package > 2.0K./service > 4.0K./lost+found > 43M. > 43Mtotal > Do these look normal or average, compare total with df - k output of /dev/ad0s1a I don't quite know what next to do -- View this message in context: http://www.nabble.com/Inconsistency-in-root-partition-size-tp25314145p25334820.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: Inconsistency in root partition size
Galactic_Dominator wrote: > > Sun, Sep 6, 2009 at 9:24 PM, jaymax wrote: > > >> >> Mel Flynn-2 wrote: >> > > > -- >> >> ufs by default keeps a certain portion in reserve for use by root. 8% is > the standard amount I believe so that capacity reading is technically > valid. On rare occasion, I've had to run fsck multiple times. you may > wish > to try this also, w/ no reboot in between. > > > I ran fsck -vy 10 times, status unchanged > > Is there somewhere I can find a listing of files and directories that are > supposed to be at the / level? if there is perchance some bizarre file, > that du is not accounting for. > > Thanks! > > -- > 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" > > -- View this message in context: http://www.nabble.com/Inconsistency-in-root-partition-size-tp25314145p25325443.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: Inconsistency in root partition size
Mel Flynn-2 wrote: > > > No, single user mode. Root partition in single user mode can be fsck'd and > repaired if mounted ro in single user. The system does fsck -p by default, > which skips partitions marked clean. Since you can shutdown cleanly, > nothing > will happen. > Have a look at /etc/defaults/rc.conf for setting different behaviors by > overriding the defaults in /etc/rc.conf. > In single user mode I ran fsck -vy / there were a few Salvages along the way Rebooted but the condition remained unchanged. rebooted again in single user mode ran fsck -vy /dev/ad0s1a everything seemed clear - no salvage operation Normal reboot, but discrepancy still persits Hope we have not reached a checkmate! from the logs the only things discernable, were dmesg => > ad0: 39083MB at ata0-master UDMA100 > ad1: 76345MB at ata0-slave UDMA100 > acd0: CDROM at ata1-master UDMA33 > acd1: DVDR at ata1-slave UDMA33 > ad4: 381554MB at ata2-master UDMA100 > Trying to mount root from ufs:/dev/ad0s1a > WARNING: /usr was not properly dismounted > WARNING: /disk02 was not properly dismounted > WARNING: /disk03 was not properly dismounted > from /var/all.log the record for today Earlier mount attempt # grep -in ad0s1a all.log 143:Sep 6 02:23:41 mach_1 kernel: Trying to mount root from ufs:/dev/ad0s1a 158:Sep 6 02:23:41 mach_1 kernel: /dev/ad0s1a: DEFER FOR BACKGROUND CHECKING 472:Sep 6 02:25:02 mach_1 fsck: /dev/ad0s1a: CANNOT CREATE SNAPSHOT //.snap/fsck_snapshot: No space left on device 474:Sep 6 02:25:02 mach_1 fsck: /dev/ad0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. 985:Sep 6 03:11:21 mach_1 kernel: Trying to mount root from ufs:/dev/ad0s1a 1000:Sep 6 03:11:21 mach_1 kernel: /dev/ad0s1a: DEFER FOR BACKGROUND CHECKING 1315:Sep 6 03:13:08 mach_1 fsck: /dev/ad0s1a: CANNOT CREATE SNAPSHOT //.snap/fsck_snapshot: No space left on device 1317:Sep 6 03:13:08 mach_1 fsck: /dev/ad0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. last mount 6311:Sep 6 17:39:33 mach_1 kernel: Trying to mount root from ufs:/dev/ad0s1a 6325:Sep 6 17:39:33 mach_1 kernel: /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS 6326:Sep 6 17:39:33 mach_1 kernel: /dev/ad0s1a: clean, 1982 free (1966 frags, 2 blocks, 0.8% fragmentation) 6772:Sep 6 17:51:19 mach_1 kernel: Trying to mount root from ufs:/dev/ad0s1a 6786:Sep 6 17:51:19 mach_1 kernel: /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS 6787:Sep 6 17:51:19 mach_1 kernel: /dev/ad0s1a: clean, 1968 free (1968 frags, 0 blocks, 0.8% fragmentation) and df -k => df -k Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad0s1a507630503694 -36674 108%/ Don't know if the above can show anything Could this be a kernel issue, tuning etc? Thanks! -- View this message in context: http://www.nabble.com/Inconsistency-in-root-partition-size-tp25314145p25324178.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: Inconsistency in root partition size
Mel Flynn-2 wrote: > > On Sunday 06 September 2009 04:34:20 jaymax wrote: >> I apparently have open file handles in my / partitions. >> It was partitioned at 512 Mb size, used about 150Mb >> df shows >> Filesystem SizeUsed Avail Capacity Mounted on >> /dev/ad0s1a496M492M-36M 108%/ > >> adjkerntz 147 root0uVBAD >> (revoked) adjkerntz 147 root1uVBAD > > >> Can't really identify lines I can say does not belong so I don't have any >> rational basis to kill any process. All seems legit! >> >> Rebooting does not correct the descrepancy > > For one, you could've used fstat -f / to reduce the noise. Secondly, since You were correct fstat -f / showed no open files handles rebooting does not help, open files are not the cause. Rather the VBAD up > there. Do an fsck -y. Chances are your file system got filled, a hardware > write error occurred and the kernel could therefore not return the space > to > the disk. > If you still have logs, I would grep for WRITE_DMA in > ran fsck on / mounted partition, is that reasonable or possible, since it is / or do I have to use a livefs disk like Fixit or Frenzy for this # fsck -vy -B /dev/ad0s1a start / wait fsck_ufs -y -F /dev/ad0s1a start / wait fsck_ufs -y -B /dev/ad0s1a /: write failed, filesystem is full CANNOT CREATE SNAPSHOT //.snap/fsck_snapshot: No space left on device ** /dev/ad0s1a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=3417 OWNER=root MODE=100400 SIZE=0 MTIME=Sep 6 02:41 2009 RECONNECT? no CLEAR? no UNREF FILE I=3495 OWNER=root MODE=140666 SIZE=0 MTIME=Sep 5 01:17 2009 CLEAR? no UNREF FILE I=3524 OWNER=root MODE=100644 SIZE=154 MTIME=Sep 5 01:23 2009 RECONNECT? no CLEAR? no ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no 16849 files, 251849 used, 1966 free (1966 frags, 0 blocks, 0.8% fragmentation) - # grep -in WRITE_DMA /var/log/messages Yielded nothing either Rebooted - came back up with the same condition. On rebooting, doesn't the system run fsck -y before mounting the disks Still stuck, at least we have eliminated the "open file handler" belief Thanks -- View this message in context: http://www.nabble.com/Inconsistency-in-root-partition-size-tp25314145p25316313.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"
Inconsistency in root partition size
I apparently have open file handles in my / partitions. It was partitioned at 512 Mb size, used about 150Mb df shows Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a496M492M-36M 108%/ alert condition output /: write failed, filesystem is full and a constant stream of error messages to console __ I ran lsof which produced a list of 2083 files Randomly selected portions produced the composite below COMMANDPID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME init 1 root cwd VDIR 0,96 1024 2 / init 1 root txt VREG 0,96 474576 41282 /sbin/init adjkerntz 147 root cwd VDIR 0,96 1024 2 / adjkerntz 147 root rtd VDIR 0,96 1024 2 / adjkerntz 147 root0uVBAD (revoked) adjkerntz 147 root1uVBAD (revoked) devd254 root txt VREG 0,96 262516 41258 /sbin/devd devd254 root0uVCHR 0,240t0 24 /dev/null syslogd 292 root txt VREG 0,96 41908 231 /lib/libutil.so.5 syslogd 292 root txt VREG 0,96 877604 236 /lib/libc.so.6 amd 413 root txt VREG 0,96 136984 808 /libexec/ld-elf.so.1 amd 413 root txt VREG 0,96 877604 236 /lib/libc.so.6 amd 413 root0uVCHR 0,240t0 24 /dev/null nfsd457 root txt VREG 0,96 877604 236 /lib/libc.so.6 nfsd457 root0uVCHR 0,240t0 24 /dev/null usbd484 root txt VREG 0,101 14964 3653493 /usr/sbin/usbd smbd500 root txt VREG 0,101 121414 1941471 /usr/local/lib/libcups.so.2 smbd500 root txt VREG 0,101 445658 3535409 /usr/local/lib/compat/pkg/libgnutls.so.12 nmbd502 root txt VREG 0,101 445658 3535409 /usr/local/lib/compat/pkg/libgnutls.so.12 nmbd502 root txt VREG 0,101 340795 1941251 /usr/local/lib/libgcrypt.so.13 httpd 504 root txt VREG 0,96 28676 225 /lib/libcrypt.so.3 httpd 504 root txt VREG 0,96 877604 236 /lib/libc.so.6 httpd 508 nobody 15wVREG 0,1011272700 2340767 /usr/local/apache/logs/error_log httpd 512 root txt VREG 0,101 952544 966860 /usr/local/apache2/bin/httpd httpd 512 root txt VREG 0,96 136984 808 /libexec/ld-elf.so.1 httpd 512 root txt VREG 0,96 98120 227 /lib/libm.so.4 httpd 512 root txt VREG 0,101 280725 966866 /usr/local/apache2/lib/libaprutil-1.so.3 httpd 512 root txt VREG 0,101 157398 1942626 /usr/local/lib/libexpat.so.6 httpd 512 root txt VREG 0,101 423490 966861 /usr/local/apache2/lib/libapr-1.so.3 httpd 512 root txt VREG 0,96 28676 225 /lib/libcrypt.so.3 httpd 512 root txt VREG 0,101 140112 3653763 /usr/lib/libpthread.so.2 httpd 512 root txt VREG 0,96 877604 236 /lib/libc.so.6 httpd 512 root txt VREG 0,101 355787 1941402 /usr/local/lib/libapr-1.so.0 httpd 512 root txt VREG 0,101 22323 95 /usr/local/apache2/modules/mod_authn_file.so httpd 512 root txt VREG 0,101 22612 96 /usr/local/apache2/modules/mod_authn_dbm.so httpd 512 root 20wVREG 0,101 274254 966466 /usr/local/apache2/logs/error_log rwhod 548 daemon txt VREG 0,101 10912 3653467 /usr/sbin/rwhod rwhod 548 daemon txt VREG 0,96 136984 808 /libexec/ld-elf.so.1 httpd 570 nobody txt VREG 0,101 23956 966670 /usr/local/apache2/modules/mod_authz_host.so httpd 570 nobody txt VREG 0,101 26206 966671 /usr/local/apache2/modules/mod_authz_groupfile.so httpd 570 nobody txt VREG 0,101 20770 966672 /usr/local/apache2/modules/mod_authz_user.so sshd586 root txt VREG 0,101 168488 3651348 /usr/sbin/sshd sshd586 root txt VREG 0,96 136984 808 /libexec/ld-elf.so.1 sendmail591 root txt VREG 0,101 27812 3653790 /usr/lib/libwrap.so.4 sendmail591 root txt VREG 0,101 184752 3653852 /usr/lib/libssl.so.4 cron614 root txt VREG 0,101 30748 3653316 /usr/sbin/cron cron614 root txt VREG 0,96 136984 808 /libexec/ld-elf.so.1 moused 717 root txt VREG 0,101 32480 3653390 /usr/sbin/moused moused 717 root txt VREG 0,96 136984 808 /libexec/ld-elf.so.1 inetd 739 root rtd VDIR 0,96 1024 2 / inetd 739 root txt VR
Cant remove /var, in relocating /var to a symbolic link
I am attempting to relocate /var to avoid files system full issues. Using a - mkdir /usr/var cd /var tar cf - . | (cd /usr/var; tar xf - ) cd / rm -rf /var ln -s /usr/var /var approach at the rm -rf /var step, the following was received rm: /var/empty: Operation not permitted rm: /var/named/dev: Device busy rm: /var/named: Directory not empty rm: /var: Device busy Te contents of /var at this site was ls /var ./ ../ empty/ named/ and ls /var/empty/ ./ ../ ls -l /var/empty/ total 4 dr-xr-xr-x 2 root wheel 512 Nov 3 2005 ./ drwxr-xr-x 4 root wheel 512 Oct 6 14:02 ../ Can't change permissons either chmod 755 /var/empty/ chmod: /var/empty/: Operation not permitted while ls /var/named/ ./ ../ dev/ ls -l /var/named/ total 5 drwxr-xr-x 3 root wheel 512 Oct 4 19:46 ./ drwxr-xr-x 5 root wheel 512 Oct 6 14:16 ../ dr-xr-xr-x 4 root wheel 512 Jan 1 2002 dev/ ls -l /var/named/dev total 0 Could chmod755 but still cant remove, dev, dir empty but => Device busy How can I remove these two directories so that I can create a link from /usr/var to /var -- View this message in context: http://www.nabble.com/Cant-remove--var%2C-in-relocating--var-to-a-symbolic-link-tp19847627p19847627.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 "[EMAIL PROTECTED]"
