Re: [OpenIndiana-discuss] Dying iSCSI Initiator
very strange so i got some basic questions : are you using only one path ? are you using jumbo frames ( host, storage, switch ) iscsi services are up i guess from storage side are you able to see the initiator host ? Gonzalo Seoane 2012/12/1 James Relph > Hi Gonzalo, > > Thanks for the reply. Nothing in the logs on the storage server (which is > OI151a7 so I would expect fairly decent compatibility!), and the IQNs > definitely haven't changed. > > Bit of a puzzler. > > James > > Principal Consultant > www.themacplace.co.uk > > > On 30 Nov 2012, at 20:17, Gonzalo Seoane wrote: > > > Hi james, > > Could you check any message from storage console? > > Check the initiator iqn mame, maybe for some reason change and iscsi > group > > on storage side must change. > > Also its good to know you have scripts from storage vendors who check any > > error on server side and solve it. > > I dont know wich one u use ( storage ) > > El 30/11/2012 17:08, "James Relph" escribió: > > > >> Hi all, > >> > >> I wonder if anyone has seen this problem before. We're running OI 151a7 > >> under VMware 5. We had the system go down (hardware failure > effectively) > >> and when we brought it back up, it can no longer access any iscsi > targets > >> (also OI 151a7, but running on baremetal on the storage side). > >> > >> The system is actually unresponsive unless I boot with milestone=none > and > >> clear the iSCSI configuration. The server can ping, ssh and otherwise > >> connect fine to the storage servers, but we get lots of: > >> > >> iscsi discovery failure - SendTargets (x.x.x.x) > >> > >> errors. If I reboot to milestone=none, I can wipe out the iSCSI config > >> and the machine will boot fine. In /var/adm/messages we get: > >> > >> iscsi session resource is in use > >> > >> but I can't find anything that seems relevant when searching for that. > >> > >> I'd be grateful for any tips! > >> > >> Thanks, > >> > >> James > >> > >> Principal Consultant > >> > >> Website:www.themacplace.co.uk > >> ___ > >> OpenIndiana-discuss mailing list > >> OpenIndiana-discuss@openindiana.org > >> http://openindiana.org/mailman/listinfo/openindiana-discuss > >> > > ___ > > OpenIndiana-discuss mailing list > > OpenIndiana-discuss@openindiana.org > > http://openindiana.org/mailman/listinfo/openindiana-discuss > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] recompile apache2 suexec how to?
On 2012-12-01 16:26, carl brunning wrote: HI Jim Thank for that information --with-suexec-userdir=DIR is what i have to do But this is not a command this is what I have to compile. Well, according to that documentation, this compiled parameter sets the subdir under user's home (from /etc/passwd), such as "public_html", that would be used to suexec scripts owned by a user when processing the Apache's "UserDir" option. If I read (and remember) this correctly, then as long as your users' scripts are anywhere under "/home/$username/public_html", the compiled "suexec-userdir=/home" should work. > The change is to do with the path as the default is /var/apache2/2.2/htdocs > And i need it to look in /home What you described in the original post seems more like the second option, --with-suexec-docroot, no? //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] recompile apache2 suexec how to?
HI Jim Thank for that information --with-suexec-userdir=DIR is what i have to do But this is not a command this is what I have to compile. This is the stuff that I hard coded when it compile Seem I have to just keep trying to compile it I hope I can do it. Just need to get the source code and try May still give the latest apache a try as it got more stuff in it that I may need to have. Time for me to sit down and see if i can compile the code and hope it works lol Thanks Carl -Original Message- From: Jim Klimov [mailto:jimkli...@cos.ru] Sent: 01 December 2012 11:49 To: openindiana-discuss@openindiana.org Subject: Re: [OpenIndiana-discuss] recompile apache2 suexec how to? On 2012-12-01 12:32, carl brunning wrote: > Thank for the update > All of apache is working but the modular suexec that is in > /usr/apache2/2.2.bin is the only thing that wrong Seem apaches has > hardcode the path in it and the instruction every were is to recompile that > So don't need to do the whole apache. > > But if i can get to compile the latest version of apache then it be > worth it > > But last time i compile that was on linux and am sure apache2.2 was done > using sun compile not gcc. > So not sure how much need to be change to get apache to compile using > gcc IIRC "suexec" is a standalone executable binary with the setuid bit set (in POSIX FS attrs). So if you want a drop-in replacement, you can pick the same version of Apache sources as are used in the package and just compile (with whatever compiler) and copy over the suexec program. I hope this would work =) Also, don't the webserver settings (DocumentRoot, UserDir) provide the behavior you need with the existing binary? From http://httpd.apache.org/docs/2.2/suexec.html : --with-suexec-userdir=DIR Define to be the subdirectory under users' home directories where suEXEC access should be allowed. All executables under this directory will be executable by suEXEC as the user so they should be "safe" programs. If you are using a "simple" UserDir directive (ie. one without a "*" in it) this should be set to the same value. suEXEC will not work properly in cases where the UserDir directive points to a location that is not the same as the user's home directory as referenced in the passwd file. Default value is "public_html". If you have virtual hosts with a different UserDir for each, you will need to define them to all reside in one parent directory; then name that parent directory here. If this is not defined properly, "~userdir" cgi requests will not work! --with-suexec-docroot=DIR Define as the DocumentRoot set for Apache. This will be the only hierarchy (aside from UserDirs) that can be used for suEXEC behavior. The default directory is the --datadir value with the suffix "/htdocs", e.g. if you configure with "--datadir=/home/apache" the directory "/home/apache/htdocs" is used as document root for the suEXEC wrapper. //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Dying iSCSI Initiator
Hi Gonzalo, Thanks for the reply. Nothing in the logs on the storage server (which is OI151a7 so I would expect fairly decent compatibility!), and the IQNs definitely haven't changed. Bit of a puzzler. James Principal Consultant www.themacplace.co.uk On 30 Nov 2012, at 20:17, Gonzalo Seoane wrote: > Hi james, > Could you check any message from storage console? > Check the initiator iqn mame, maybe for some reason change and iscsi group > on storage side must change. > Also its good to know you have scripts from storage vendors who check any > error on server side and solve it. > I dont know wich one u use ( storage ) > El 30/11/2012 17:08, "James Relph" escribió: > >> Hi all, >> >> I wonder if anyone has seen this problem before. We're running OI 151a7 >> under VMware 5. We had the system go down (hardware failure effectively) >> and when we brought it back up, it can no longer access any iscsi targets >> (also OI 151a7, but running on baremetal on the storage side). >> >> The system is actually unresponsive unless I boot with milestone=none and >> clear the iSCSI configuration. The server can ping, ssh and otherwise >> connect fine to the storage servers, but we get lots of: >> >> iscsi discovery failure - SendTargets (x.x.x.x) >> >> errors. If I reboot to milestone=none, I can wipe out the iSCSI config >> and the machine will boot fine. In /var/adm/messages we get: >> >> iscsi session resource is in use >> >> but I can't find anything that seems relevant when searching for that. >> >> I'd be grateful for any tips! >> >> Thanks, >> >> James >> >> Principal Consultant >> >> Website:www.themacplace.co.uk >> ___ >> OpenIndiana-discuss mailing list >> OpenIndiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss >> > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] recompile apache2 suexec how to?
Have looked at the files in /etc/apache/2.2/examples? It has a file that explains how to share user directories. Kind regards, The out-side Op 30 nov. 2012 om 23:03 heeft carl brunning het volgende geschreven: > Hi > I have a problem with suexec, as it has hard code path it seem you need to > recompile > > What i need to know is where the source and how do i compile it > > The change is to do with the path as the default is /var/apache2/2.2/htdocs > And i need it to look in /home > > Any one got a new suexe with the path, or a very good set of instruction on > how to do it my self > > > > Thanks > Carl > > ___ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] recompile apache2 suexec how to?
On 2012-12-01 12:32, carl brunning wrote: Thank for the update All of apache is working but the modular suexec that is in /usr/apache2/2.2.bin is the only thing that wrong Seem apaches has hardcode the path in it and the instruction every were is to recompile that So don't need to do the whole apache. But if i can get to compile the latest version of apache then it be worth it But last time i compile that was on linux and am sure apache2.2 was done using sun compile not gcc. So not sure how much need to be change to get apache to compile using gcc IIRC "suexec" is a standalone executable binary with the setuid bit set (in POSIX FS attrs). So if you want a drop-in replacement, you can pick the same version of Apache sources as are used in the package and just compile (with whatever compiler) and copy over the suexec program. I hope this would work =) Also, don't the webserver settings (DocumentRoot, UserDir) provide the behavior you need with the existing binary? From http://httpd.apache.org/docs/2.2/suexec.html : --with-suexec-userdir=DIR Define to be the subdirectory under users' home directories where suEXEC access should be allowed. All executables under this directory will be executable by suEXEC as the user so they should be "safe" programs. If you are using a "simple" UserDir directive (ie. one without a "*" in it) this should be set to the same value. suEXEC will not work properly in cases where the UserDir directive points to a location that is not the same as the user's home directory as referenced in the passwd file. Default value is "public_html". If you have virtual hosts with a different UserDir for each, you will need to define them to all reside in one parent directory; then name that parent directory here. If this is not defined properly, "~userdir" cgi requests will not work! --with-suexec-docroot=DIR Define as the DocumentRoot set for Apache. This will be the only hierarchy (aside from UserDirs) that can be used for suEXEC behavior. The default directory is the --datadir value with the suffix "/htdocs", e.g. if you configure with "--datadir=/home/apache" the directory "/home/apache/htdocs" is used as document root for the suEXEC wrapper. //Jim ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] recompile apache2 suexec how to?
Thank for the update All of apache is working but the modular suexec that is in /usr/apache2/2.2.bin is the only thing that wrong Seem apaches has hardcode the path in it and the instruction every were is to recompile that So don't need to do the whole apache. But if i can get to compile the latest version of apache then it be worth it But last time i compile that was on linux and am sure apache2.2 was done using sun compile not gcc. So not sure how much need to be change to get apache to compile using gcc That why am asking for nice instruction lol Anyway thanks for the head up about the userland i will try to look soon Thanks Carl Brunning -Original Message- From: Jim Klimov [mailto:jimkli...@cos.ru] Sent: 01 December 2012 10:08 To: Discussion list for OpenIndiana Subject: Re: [OpenIndiana-discuss] recompile apache2 suexec how to? On 2012-11-30 23:03, carl brunning wrote: > Hi > I have a problem with suexec, as it has hard code path it seem you > need to recompile > > What i need to know is where the source and how do i compile it > > The change is to do with the path as the default is > /var/apache2/2.2/htdocs And i need it to look in /home > > Any one got a new suexe with the path, or a very good set of > instruction on how to do it my self Do you mean to replace specifically the packaged build for OI, or just need to compile a version of your own (i.e. residing in another path or overriding the package - at your discretion)? In any case, for "source" and "how to" does the original suffice? Here: * http://httpd.apache.org/ * http://httpd.apache.org/docs/current/suexec.html For the OI packaging replacement, I guess you'd need to find the build recipe somewhere in SFE or userland gate, and adapt it to your needs, and publish on your internal IPS repo server. HTH, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] recompile apache2 suexec how to?
On 2012-11-30 23:03, carl brunning wrote: Hi I have a problem with suexec, as it has hard code path it seem you need to recompile What i need to know is where the source and how do i compile it The change is to do with the path as the default is /var/apache2/2.2/htdocs And i need it to look in /home Any one got a new suexe with the path, or a very good set of instruction on how to do it my self Do you mean to replace specifically the packaged build for OI, or just need to compile a version of your own (i.e. residing in another path or overriding the package - at your discretion)? In any case, for "source" and "how to" does the original suffice? Here: * http://httpd.apache.org/ * http://httpd.apache.org/docs/current/suexec.html For the OI packaging replacement, I guess you'd need to find the build recipe somewhere in SFE or userland gate, and adapt it to your needs, and publish on your internal IPS repo server. HTH, //Jim Klimov ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
