Re: replicating /etc/passwd on a failover machine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 thanks for the help guys ! Jerry McAllister wrote: On Wed, Dec 20, 2006 at 11:28:27AM -0500, stas khromoy wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hey folks we are working on building a failover server. now everything is going along pretty nicely. (knock on wood) so the question of the day. is there a way to replicate the password files ? i doubt that just copying over /etc/passwd and master.passwd will work . Almost. You just need to make sure database stuff is updated properly. Check out pwd_mkdb(8) and vipw(8) and man master.passwd and man passwd. jerry thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRYwRJNbpM15f9s9nAQI4fQP9FR2s+YClP9fWLN1uBHH/0gBr6zl2ai6S tIMNCav8rfj+xZlWJiN723WBp5U9O3msv7edHD1jPUfkVblZOp096jI976nYfE1D vVvaQ5qAtTk3zJ/SsgKkusOIG6J1WCmif+WY26VBEkHLLkIvUI3AeCPyygRtbdyv Kg4YsT4IlJk= =IlD/ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
replicating /etc/passwd on a failover machine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hey folks we are working on building a failover server. now everything is going along pretty nicely. (knock on wood) so the question of the day. is there a way to replicate the password files ? i doubt that just copying over /etc/passwd and master.passwd will work . thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRYlkq9bpM15f9s9nAQKnRwP/ZXN9rExeMteW6GW60a1sECMgoxJ+s0lv v3BrIWKoqV+seWs1yPTJx8y4k46ji55wMbWHwKy3tK0d1Ok/uaJRkS8NYlcQxJJo UgDwW+sAovyG7QpLCGMJp5qCSYii1WPGa/O1NOzMjKerVIpT7AuO5s5nXWd0hg1S JuQnoqLNhL8= =MXb4 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd install on poweredge 2900
hey folks trying to install freebsd 6.1 on dell's poweredge 2900 6 hard drives on *perc 5/i integrated controller ( the drives are 146gb SAS). i've set up raid 1 for the first 2 drives and raid 10 for the remaining 4 . everything is showing up tip-top in the controller configuration one virtual drive is 146gb the other one is 280gb when i finally get to partioning menu during the FreeBSD install i see two volumes, problem is both of them are showing up as 146GB. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pfstat error
hey folks after upgrading to FreeBSD 6.1 pfstat runs with the following error pfstat: ioctl(DIOCGETSTATUS): Operation not supported by device ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dell poweregde 2900/2950 and FreeBSD
hey folks we're planing to expand, which of course requires us to buy another server. so here is the question are there any known problems with dell PowerEdge 2900/2950 and FreeBSD ? thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
scsi troubles
hey folks we've been getting scsi errors during tape backups using dump. most of the time the backups complete without any problems but once every 20-30 or so runs we get an error like the one bellow we are running dell poweredge 2600 with powervault 114t LTO2 tape drive FreeBSD 5.4-RELEASE-p7 FreeBSD 5.4-RELEASE-p7 #2: Fri Oct 7 22:49:12 EDT 2005 i386 bellow is the error and some other handy info (let me know if this isn't enough) - Apr 20 08:23:10 server kernel: ahc0: Adaptec 3960D Ultra160 SCSI adapter port 0xec00-0xecff mem 0xfdcff000-0xfdcf irq 24 at device 2.0 on pci2 Apr 20 08:23:10 server kernel: aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs Apr 20 08:23:10 server kernel: ahc1: Adaptec 3960D Ultra160 SCSI adapter port 0xe800-0xe8ff mem 0xfdcfe000-0xfdcfefff irq 25 at device 2.1 on pci2 Apr 20 08:23:10 server kernel: aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs Apr 20 08:23:10 server kernel: Waiting 15 seconds for SCSI devices to settle Apr 20 08:23:10 server kernel: sa0: IBM ULTRIUM-TD2 3AYC Removable Sequential Access SCSI-3 device Apr 20 08:23:10 server kernel: ses0: PE/PV 1x2 SCSI BP 1.1 Fixed Processor SCSI-2 device Apr 20 08:23:10 server kernel: ses1: PE/PV 1x6 SCSI BP 1.1 Fixed Processor SCSI-2 device 000 Mar 30 23:30:19 server kernel: ahc0: Dumping Card State while idle, at SEQADDR 0x8 Mar 30 23:30:19 server kernel: Card was paused Mar 30 23:30:19 server kernel: ACCUM = 0x4, SINDEX = 0x67, DINDEX = 0x27, ARG_2 = 0x3 Mar 30 23:30:19 server kernel: HCNT = 0x0 SCBPTR = 0x0 Mar 30 23:30:19 server kernel: SCSIPHASE[0x0] SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0] Mar 30 23:30:19 server kernel: LASTPHASE[0x1]:(P_BUSFREE) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) Mar 30 23:30:19 server kernel: SBLKCTL[0xa]:(SELWIDE|SELBUSB) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE) Mar 30 23:30:19 server kernel: SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SSTAT0[0x0] Mar 30 23:30:19 server kernel: SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] SIMODE0[0x8]:(ENSWRAP) Mar 30 23:30:19 server kernel: SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) SXFRCTL0[0x80]:(DFON) Mar 30 23:30:19 server kernel: DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) Mar 30 23:30:19 server kernel: STACK: 0x0 0x164 0x179 0x3 Mar 30 23:30:19 server kernel: SCB count = 20 Mar 30 23:30:19 server kernel: Kernel NEXTQSCB = 3 Mar 30 23:30:19 server kernel: Card NEXTQSCB = 3 Mar 30 23:30:19 server kernel: QINFIFO entries: Mar 30 23:30:19 server kernel: Waiting Queue entries: Mar 30 23:30:19 server kernel: Disconnected Queue entries: 0:14 Mar 30 23:30:19 server kernel: QOUTFIFO entries: Mar 30 23:30:19 server kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Mar 30 23:30:19 server kernel: Sequencer SCB Info: Mar 30 23:30:19 server kernel: 0 SCB_CONTROL[0x44]:(DISCONNECTED|DISCENB) SCB_SCSIID[0x67] Mar 30 23:30:19 server kernel: SCB_LUN[0x0] SCB_TAG[0xe] Mar 30 23:30:19 server kernel: 1 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 2 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 3 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 4 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 5 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 6 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 7 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 8 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 9 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 10 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 11 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID) Mar 30 23:30:19 server kernel: SCB_LUN[0xff]:(SCB_XFERLEN_ODD|LID) SCB_TAG[0xff] Mar 30 23:30:19 server kernel: 12 SCB_CONTROL[0x0] SCB_SCSIID[0xff]:(TWIN_CHNLB|OID|TWIN_TID)
Re: scsi troubles
i am pretty sure backups don't work when error comes up and the tape drive locks up at that time too, requiring a cold reset is any one else using this tape model (powervault 114t LTO2 tape drive)? - [snip] Do you know for sure if the backups are failing? It's possible the dump card states are harmless. I have some systems that do a dump card state on boot but that have never exhibited an actual problem. Another suggestion is to check if you have the latest firmware for both the tape drive and the controller. Still more people will probably say that there is bad voodoo between whoever your controller vendor is and whoever your drive vendor is. Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi troubles
Mike: maybe i am blind and don't see this info in your reply do you use Adaptec 3960D scsi adapter ? Mike Galvez wrote: On Thu, Apr 20, 2006 at 12:35:59PM -0400, Stas Khromoy wrote: i am pretty sure backups don't work when error comes up and the tape drive locks up at that time too, requiring a cold reset is any one else using this tape model (powervault 114t LTO2 tape drive)? Stas, I am using a PV-124T LTO2. I am having similar issues with the changer locking up when moving tapes. I didn't see the earlier part of this thread, so I don't know what you are using for backup software. I'm using Amanda 2.4.5p1 with FreeBSD 6.1-RC1 on Dell PE-850 and having a few issues getting it to run smoothly. I was beginning to wonder if I got a bad changer. I am able to make backups and restore from them, but every so often I get a Dump Card State message and the changer locks up and has to be power-cycled. ch0 at ahc0 bus 0 target 6 lun 1 ch0: DELL PV-124T 0026 Removable Changer SCSI-2 device ch0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) ch0: 8 slots, 1 drive, 1 picker, 0 portals (sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. (sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. ahc0: Recovery Initiated Dump Card State Begins ahc0: Dumping Card State while idle, at SEQADDR 0x8 Card was paused ACCUM = 0x4, SINDEX = 0x67, DINDEX = 0x27, ARG_2 = 0x4 HCNT = 0x0 SCBPTR = 0x0 SCSIPHASE[0x0] SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0] LASTPHASE[0x1]:(P_BUSFREE) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) SBLKCTL[0xa]:(SELWIDE|SELBUSB) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE) SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SSTAT0[0x0] - snip This probably isn't helpful as I don't have an answer for why this happening. I'm still looking. -Mike - [snip] Do you know for sure if the backups are failing? It's possible the dump card states are harmless. I have some systems that do a dump card state on boot but that have never exhibited an actual problem. Another suggestion is to check if you have the latest firmware for both the tape drive and the controller. Still more people will probably say that there is bad voodoo between whoever your controller vendor is and whoever your drive vendor is. Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi troubles
alright i will try the firmare and will try changing the adapter if firmware will not help will let you know about the results. Mike Galvez wrote: On Thu, Apr 20, 2006 at 04:22:11PM -0400, Stas Khromoy wrote: Mike: maybe i am blind and don't see this info in your reply do you use Adaptec 3960D scsi adapter ? Stas, You're not blind, I just forgot to add the info, The adapter was also purchased through Dell and is Adaptec 3960D Ultra160 SCSI adapter hth -Mike Mike Galvez wrote: On Thu, Apr 20, 2006 at 12:35:59PM -0400, Stas Khromoy wrote: i am pretty sure backups don't work when error comes up and the tape drive locks up at that time too, requiring a cold reset is any one else using this tape model (powervault 114t LTO2 tape drive)? Stas, I am using a PV-124T LTO2. I am having similar issues with the changer locking up when moving tapes. I didn't see the earlier part of this thread, so I don't know what you are using for backup software. I'm using Amanda 2.4.5p1 with FreeBSD 6.1-RC1 on Dell PE-850 and having a few issues getting it to run smoothly. I was beginning to wonder if I got a bad changer. I am able to make backups and restore from them, but every so often I get a Dump Card State message and the changer locks up and has to be power-cycled. ch0 at ahc0 bus 0 target 6 lun 1 ch0: DELL PV-124T 0026 Removable Changer SCSI-2 device ch0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) ch0: 8 slots, 1 drive, 1 picker, 0 portals (sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. (sa0:ahc0:0:6:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. ahc0: Recovery Initiated Dump Card State Begins ahc0: Dumping Card State while idle, at SEQADDR 0x8 Card was paused ACCUM = 0x4, SINDEX = 0x67, DINDEX = 0x27, ARG_2 = 0x4 HCNT = 0x0 SCBPTR = 0x0 SCSIPHASE[0x0] SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0] LASTPHASE[0x1]:(P_BUSFREE) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) SBLKCTL[0xa]:(SELWIDE|SELBUSB) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE) SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SSTAT0[0x0] - snip This probably isn't helpful as I don't have an answer for why this happening. I'm still looking. -Mike - [snip] Do you know for sure if the backups are failing? It's possible the dump card states are harmless. I have some systems that do a dump card state on boot but that have never exhibited an actual problem. Another suggestion is to check if you have the latest firmware for both the tape drive and the controller. Still more people will probably say that there is bad voodoo between whoever your controller vendor is and whoever your drive vendor is. Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
