Discuss

discuss@lists.centos.org

34753 discussions

can't disconnec iSCSI targets, please help
by Rudi Ahlers 28 Feb '11

28 Feb '11

Hi, I'm trying to disconnect some iSCSI targets, but can't seem to. [root@localhost ~]# iscsiadm -m session tcp: [1] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:500gb tcp: [3] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba tcp: [4] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:extent0 tcp: [5] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.iscsi0.vg0.500gb I need to disconnect all 4 of these [root@localhost ~]# iscsiadm -m node -T 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.iscsi0.vg0.500gb -p 196.34.136.200 --logout The target is still there, even though I tell it to disconnect. [root@localhost ~]# iscsiadm -m session tcp: [1] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:500gb tcp: [3] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba tcp: [4] 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:extent0 tcp: [5] 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.iscsi0.vg0.500gb I can't delete it either: [root@localhost ~]# iscsiadm -m node --op delete --targetname 192.168.2.202:3260,1 iqn.2011.01.22.freenas.nvr:500gb iscsiadm: no records found! Restarting iscsi gives some odd errors: [root@localhost ~]# /etc/init.d/iscsi restart Logging out of session [sid: 1, target: iqn.2011.01.22.freenas.nvr:500gb, portal: 192.168.2.202,3260] Logging out of session [sid: 3, target: iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba, portal: 192.168.2.200,3260] Logging out of session [sid: 4, target: iqn.2011.01.22.freenas.nvr:extent0, portal: 192.168.2.202,3260] Logging out of session [sid: 5, target: iqn.2011-2.za.co.securehosting:RAID.iscsi0.vg0.500gb, portal: 192.168.2.200,3260] Logout of [sid: 1, target: iqn.2011.01.22.freenas.nvr:500gb, portal: 192.168.2.202,3260]: successful Logout of [sid: 3, target: iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba, portal: 192.168.2.200,3260]: successful Logout of [sid: 4, target: iqn.2011.01.22.freenas.nvr:extent0, portal: 192.168.2.202,3260]: successful Logout of [sid: 5, target: iqn.2011-2.za.co.securehosting:RAID.iscsi0.vg0.500gb, portal: 192.168.2.200,3260]: successful Stopping iSCSI daemon: iscsid dead but pid file exists [ OK ] Starting iSCSI daemon: [ OK ] [ OK ] Setting up iSCSI targets: Logging in to [iface: default, target: iqn.2011.01.22.freenas.nvr:500gb, portal: 192.168.2.202,3260] Logging in to [iface: default, target: iqn.2011-2.za.co.securehosting:RAID.thin1.vg0.2tb, portal: 192.168.2.200,3260] Logging in to [iface: default, target: iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba, portal: 192.168.2.200,3260] Logging in to [iface: default, target: iqn.2011.01.22.freenas.nvr:extent0, portal: 192.168.2.202,3260] Logging in to [iface: default, target: iqn.2011-2.za.co.securehosting:RAID.iscsi0.vg0.500gb, portal: 192.168.2.200,3260] Logging in to [iface: default, target: iqn.2011-2.za.co.securehosting:RAID.thin2.vg0.1tb, portal: 192.168.2.200,3260] Login to [iface: default, target: iqn.2011.01.22.freenas.nvr:500gb, portal: 192.168.2.202,3260]: successful iscsiadm: Could not login to [iface: default, target: iqn.2011-2.za.co.securehosting:RAID.thin1.vg0.2tb, portal: 192.168.2.200,3260]: iscsiadm: initiator reported error (19 - encountered non-retryable iSCSI login failure) Login to [iface: default, target: iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba, portal: 192.168.2.200,3260]: successful Login to [iface: default, target: iqn.2011.01.22.freenas.nvr:extent0, portal: 192.168.2.202,3260]: successful Login to [iface: default, target: iqn.2011-2.za.co.securehosting:RAID.iscsi0.vg0.500gb, portal: 192.168.2.200,3260]: successful iscsiadm: Could not login to [iface: default, target: iqn.2011-2.za.co.securehosting:RAID.thin2.vg0.1tb, portal: 192.168.2.200,3260]: iscsiadm: initiator reported error (19 - encountered non-retryable iSCSI login failure) iscsiadm: Could not log into all portals. Err 19. Interestingly, the targets which iscsi reports as not existing, does exist: [root@localhost ~]# iscsiadm -m discovery -t sendtargets -p 192.168.2.200 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin1.vg0.2tb 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin3.vg0.1tba 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.iscsi0.vg0.500gb 192.168.2.200:3260,1 iqn.2011-2.za.co.securehosting:RAID.thin2.vg0.1tb Is there any other way to force these disconnects, and re-connect them? The machine runs on CentOS 5.5 x64 + XEN: [root@localhost ~]# cat /etc/redhat-release CentOS release 5.5 (Final) [root@localhost ~]# uname -a Linux localhost.localdomain 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux [root@localhost ~]# -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532

3 4

Re: [CentOS] Octet - off topic
by Always Learning 28 Feb '11

28 Feb '11

On Sun, 2011-02-27 at 22:38 -0600, Larry Vaden wrote: > On Sun, Feb 27, 2011 at 5:48 PM, Always Learning <centos(a)g7.u22.net> wrote: > > > > At my second computer job in 1967 on a Honeywell H-120 (a baby machine > > with 3 tapes which took 1 hour to do a Cobol compilation ... > I have always hoped to find someone who was involved with COBOL back > in the days to ask this question of: > > "What influence did Commander Grace Hopper have on COBOL?" Don't know. Grace was occasionally mentioned in the computer press for getting awards in the USA (I think she was in the USA Navy) but we programmers, new to a new world of computing, just wrote programmes, debugged them, did some systems analysis and ventured into assembler coding and system programming. Grace never ever influenced me or anyone else I knew who did Cobol. She was just a name to the majority who programmed in Cobol. I used to think it took someone 2 years of writing in Cobol to become efficient in using it and visualising solutions which could be implemented in it. Well written Cobol was easy to maintain but some clowns never properly used the self documenting features of the language (i.e. meaningful data names - contrast with add csum to itotal). The alternative was longer data names, for example inv-gross-total, inv-delivery-cost and overdue-3-mths-total etc. Many programmed in Cobol but fewer used the language to its designed extent. The worse thing about Cobol was the long windiness of it before one came to the Procedure Division. Later on Picture became Pic and very useful string handling was introduced (the alternative was refining the same field multiple times). It used to be my favourite language, after Easycoder and 6502 assembler, then I discovered PHP. -- With best regards, Paul. England, EU.

2 1

how to make centos safty(php+mysql)
by Yang Yang 28 Feb '11

28 Feb '11

hi,every i have a php project and use centos to go and how to make folder's privilage and make it saft like: /home/htdocs/test chown -R www:www /home/htdocs/test chmod -R 644 /home/htdocs/test etc thanks very much

4 3

Logwatch reporting spamassassin messages as unmatched entries
by Steve Searle 28 Feb '11

28 Feb '11

I've recently switched to using spamassassin via a sendmail milter, rather than using procmail to invoke it. This means that I get a number of messages appearing in my maillog, and then being reported by logwatch as unmatched entries. An example of such a messages is: Feb 27 04:33:09 quail sendmail[24780]: p1R4X46P024780[2]: URIBL blacklist\n\t* [URIs: tablettoxicspillsrx.ru]\n\t* 1.5 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist\n\t* [URIs: tablettoxicspillsrx.ru]\n\t* 1.5 URIBL_JP_SURBL Contains an URL listed in the JP SURBL blocklist\n\t* [URIs: tablettoxicspillsrx.ru]\n\t* 1.5 URIBL_SBL Contains an URL listed in the SBL blocklist\n\t* [URIs: tablettoxicspillsrx.ru]\n\t* 0.3 DRUGS_ERECTILE Refers to an erectile drug to \n\t* 3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100%\n\t* [score: 1.0000]\n\t* 0.3 DRUG_ED_CAPS BODY: Mentions an E.D. drug\n\t* 1.6 DRUG_ED_GENERIC BODY: Mentions Generic Viagra\n\t* 2.0 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net\n\t* [Blocked - see <http://www.spamcop.net/bl.shtml?93.159.243.52>]\n\t* 0.9 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL\n\t* [93.159.243.52 listed in zen.spamhaus.org]\n\t* 3.0 RCVD_IN_XBL RBL: Received via a ... Is there a "best" approach to dealing with this; for instance stopping spamassassin reporting these to the maillog, or changing logwatch to recognise the messages. And how do I change it. Thanks Steve -- Website: www.stevesearle.com Twitter: @ReddishShift Facebook: www.facebook.com/steve.searle 09:11:55 up 6 days, 10:39, 1 user, load average: 0.08, 0.02, 0.01

2 1

Re: [CentOS] IP6 Anyone?
by Always Learning 28 Feb '11

28 Feb '11

On Sun, 2011-02-27 at 00:38 -0600, Larry Vaden wrote: > On Sat, Feb 26, 2011 at 2:12 PM, Always Learning <centos(a)g7.u22.net> wrote: > > > > Today I received an allocation of IP6 addresses for some servers. I can > > 'play' with the last 2 of the 8 IP6 address segments. > > I guess Will Rogers was correct after all :) > > You can label yourself as "special" since others get assignments of > IPv4 and IPv6 addresses. > > <https://www.arin.net/policy/archive/ipv6_policy.html#25> says, in part: > > 2.5. Allocate > > To allocate means to distribute address space to IRs for the purpose > of subsequent distribution by them. > > 2.6. Assign > > To assign means to delegate address space to an ISP or end-user, for > specific use within the Internet infrastructure they operate. > Assignments must only be made for specific purposes documented by > specific organizations and are not to be sub-assigned to other > parties. I was actually wrong. I can 'play' with not 2 but 4 groups of the IP6 allocation. Golly, what can I do with 64 x 64 x 64 x 64 address combinations? Hire then out? Have a different IP6 address for every hour of the year? Put the IP4 address in the last 4 groups? (2001::10.2.2.191) That vast surplus of IP6 addresses is just for one server - I have several. -- With best regards, Paul. England, EU.

7 8

php53 and Fileinfo
by Alexander Farber 28 Feb '11

28 Feb '11

Hello, for drupal 7 installation at CentOS 5.5 (I have 32 bit and 64 bit machines) I have to upgrade PHP to 5.3. I've followed the CentOS wiki: 1) Created this file - grep -v ^# /etc/yum.repos.d/CentOS-Testing.repo [c5-testing] name=CentOS-5 Testing baseurl=http://dev.centos.org/centos/$releasever/testing/$basearch/ enabled=1 gpgcheck=1 gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing includepkgs=php* 2) Uninstalled the old PHP - rpm -qa|grep php| xargs sudo yum -y erase 3) Installed new php53: # rpm -qa |grep php php53-pgsql-5.3.3-1.el5 php53-gd-5.3.3-1.el5 php53-pdo-5.3.3-1.el5 php53-xml-5.3.3-1.el5 php53-cli-5.3.3-1.el5 php53-common-5.3.3-1.el5 php53-mbstring-5.3.3-1.el5 4) Verified php works: php -v PHP 5.3.3 (cli) (built: Jan 20 2011 23:02:42) Copyright (c) 1997-2010 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Unfortunately I need Fileinfo module too, for my script. I do not see "pecl" though and also "yum install php-pecl-Fileinfo" fails with "wrong version" error. Any help please on how to install Fileinfo? Thank you Alex

1 1

Centos Project : STEM
by Always Learning 28 Feb '11

28 Feb '11

On https://projects.centos.org/trac/stem/ there is a brief mention of Stem and VOIP with a request for dial-in numbers. However there are no links on the page describing STEM. Stem sounds a bit like the Dutch word for 'voice'. What type of dialing-in, from the PSTN, numbers are required and how can they be used to benefit Centos? -- With best regards, Paul. England, EU.

1 0

log time formats - where is this defined
by Rob Kampen 28 Feb '11

28 Feb '11

One of my servers is using ISO datetime formats (2011-02-27T15:22:15.519857-05:00) in the logs the rest use the default redhat/CentOS format (Feb 27 15:10:21). After a couple of hours searching google I cannot find where this is defined. I know I changed it some months ago as an experiment but forgotten where this was done. the ISO format breaks logwatch - thus I need to revert. TIA

3 4

opened OpenSSL port
by erikmccaskey64 28 Feb '11

28 Feb '11

Main question: is it safe, to open a port for an openssl server? e.g.: server side - generate a self-signed cert. time openssl req -x509 -nodes -days 365 -newkey rsa:8192 -keyout mycert.pem -out mycert.pem openssl s_server -accept 52310 -cert mycert.pem Is it secure? - it could be DOSed' [DenialofService] or could it be attacked in any way? Are there any iptables rule for restricting connections to dyndns names? e.g.: only allow connection from "asdfasdf.dyndns.com" and "asdfasdf2.dyndns.com" and "asdfasdf3.dyndns.com"? How could i restrict the openssl server to only accept traffic from given clients? Please help me "think".. Or are there any "production ready" methods, that can do authentication too? [+using ssl]. "openssl s_server" and "openssl s_client" would be perfect, but the problem is it doesn't has username/password auth :\ Thank you for any help.

4 3

Recover botched drdb gfs2 setup .
by Machin, Greg 28 Feb '11

28 Feb '11

Hi. The short story... Rush job, never done clustered file systems before, vlan didn't support multicast. Thus I ended up with drbd working ok between the two servers but cman / gfs2 not working, resulting in what was meant to be a drbd primary/primary cluster being a primary/secondary cluster until the vlan could be fixed with gfs only mounted on the one server. I got the single server working and left to for the contractor to do there bit. Two months down the line and a few other hiccups in the mix I have a server that wont mount the gfs partition.. assuming that drbd hasn't gotten confused and lost the data on the drive.. If I can how do I fix this. Drbd is currently as follows: [root@mcvpsam01 init.d]# drbd-overview 1:r0 WFConnection Primary/Unknown UpToDate/DUnknown C r---- Cman: [root@mcvpsam01 init.d]# /etc/init.d/cman status groupd is stopped gfs2 mount [root@mcvpsam01 init.d]# ./gfsmount.sh start Mounting gfs2 partition /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: can't connect to gfs_controld: Connection refused /sbin/mount.gfs2: gfs_controld not running /sbin/mount.gfs2: error mounting lockproto lock_dlm [root@mcvpsam01 init.d]# And log/messages Feb 28 09:20:39 mcvpsam01 openais[3328]: [TOTEM] The consensus timeout expired. Feb 28 09:20:39 mcvpsam01 openais[3328]: [TOTEM] entering GATHER state from 3. Feb 28 09:20:54 mcvpsam01 openais[3328]: [TOTEM] The consensus timeout expired. Feb 28 09:20:54 mcvpsam01 openais[3328]: [TOTEM] entering GATHER state from 3. Feb 28 09:21:09 mcvpsam01 openais[3328]: [TOTEM] The consensus timeout expired. Feb 28 09:21:09 mcvpsam01 openais[3328]: [TOTEM] entering GATHER state from 3. cluster.conf [root@mcvpsam01 init.d]# cat /etc/cluster/cluster.conf <?xml version="1.0"?> <cluster alias="cluster-setup" config_version="1" name="cluster-setup"> <rm log_level="4"/> <fence_daemon clean_start="1" post_fail_delay="0" post_join_delay="3"/> <clusternodes> <clusternode name="mcvpsam01" nodeid="1" votes="1"> <fence> <method name="2"> <device name="LastResortNode01"/> </method> </fence> </clusternode> <clusternode name="drvpsam01" nodeid="2" votes="1"> <fence> <method name="2"> <device name="LastResortNode02"/> </method> </fence> </clusternode> </clusternodes> <cman expected_votes="1" two_node="1"/> <fencedevices> <fencedevice agent="fence_manual" name="LastResortNode01" nodename="mcvpsam01"/> <fencedevice agent="fence_manual" name="LastResortNode02" nodename="drvpsam01"/> </fencedevices> <rm/> <totem consensus="4800" join="60" token="10000" token_retransmits_before_loss_const="20"/> </cluster> [root@mcvpsam01 init.d]# Drbd.conf [root@mcvpsam01 init.d]# cat /etc/drbd.conf resource r0 { protocol C; syncer { rate 1000M; } startup { wfc-timeout 120; # wait 2min for other peers degr-wfc-timeout 120; # wait 2min if peer was already # down before this node was rebooted become-primary-on both; } net { allow-two-primaries; # cram-hmac-alg "sha1"; # algo to enable peer authentication # shared-secret "123456"; # handle split-brain situations after-sb-0pri discard-least-changes;# if no primary auto sync from the # node that touched more blocks during # the split brain situation. after-sb-1pri discard-secondary; # if one primary after-sb-2pri disconnect; # if two primaries # solve the cases when the outcome # of the resync decision is incompatible # with the current role assignment in # the cluster rr-conflict disconnect; # no automatic resynchronization # simply disconnect } disk { on-io-error detach; # detach the device from its # backing storage if the driver of # the lower_device reports an error # to DRBD # fencing resource-and-stonith; } on mcvpsam01 { device /dev/drbd1; disk /dev/sdb1; address 202.37.1.133:7789; meta-disk internal; } on drvpsam01 { device /dev/drbd1; disk /dev/sdb1; address 202.37.1.134:7789; meta-disk internal; } } [root@mcvpsam01 init.d]# [root@mcvpsam01 init.d]# cat /etc/drbd.d/global_common.conf global { usage-count yes; # minor-count dialog-refresh disable-ip-verification } common { protocol C; handlers { pri-on-incon-degr "/usr/lib/drbd/notify-pri-on-incon-degr.sh; /usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ; reboot -f"; pri-lost-after-sb "/usr/lib/drbd/notify-pri-lost-after-sb.sh; /usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ; reboot -f"; local-io-error "/usr/lib/drbd/notify-io-error.sh; /usr/lib/drbd/notify-emergency-shutdown.sh; echo o > /proc/sysrq-trigger ; halt -f"; # fence-peer "/usr/lib/drbd/crm-fence-peer.sh"; # split-brain "/usr/lib/drbd/notify-split-brain.sh root"; # out-of-sync "/usr/lib/drbd/notify-out-of-sync.sh root"; # before-resync-target "/usr/lib/drbd/snapshot-resync-target-lvm.sh -p 15 -- -c 16k"; # after-resync-target /usr/lib/drbd/unsnapshot-resync-target-lvm.sh; } startup { # wfc-timeout degr-wfc-timeout outdated-wfc-timeout wait-after-sb } disk { # on-io-error fencing use-bmbv no-disk-barrier no-disk-flushes # no-disk-drain no-md-flushes max-bio-bvecs } net { # sndbuf-size rcvbuf-size timeout connect-int ping-int ping-timeout max-buffers # max-epoch-size ko-count allow-two-primaries cram-hmac-alg shared-secret # after-sb-0pri after-sb-1pri after-sb-2pri data-integrity-alg no-tcp-cork } syncer { # rate after al-extents use-rle cpu-mask verify-alg csums-alg } } [root@mcvpsam01 init.d]# Any ideas how I can get the file system mounted to recover the data. Thanks Greg Machin Systems Administrator - Linux Infrastructure Group, Information Services

1 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss