You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(10) |
Nov
(37) |
Dec
(66) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(52) |
Feb
(136) |
Mar
(65) |
Apr
(38) |
May
(46) |
Jun
(143) |
Jul
(60) |
Aug
(33) |
Sep
(79) |
Oct
(29) |
Nov
(13) |
Dec
(14) |
2006 |
Jan
(25) |
Feb
(26) |
Mar
(4) |
Apr
(9) |
May
(29) |
Jun
|
Jul
(9) |
Aug
(11) |
Sep
(10) |
Oct
(9) |
Nov
(45) |
Dec
(8) |
2007 |
Jan
(82) |
Feb
(61) |
Mar
(39) |
Apr
(7) |
May
(9) |
Jun
(16) |
Jul
(2) |
Aug
(22) |
Sep
(2) |
Oct
|
Nov
(4) |
Dec
(5) |
2008 |
Jan
|
Feb
|
Mar
(5) |
Apr
(2) |
May
(8) |
Jun
|
Jul
(10) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
(32) |
May
|
Jun
(7) |
Jul
|
Aug
(38) |
Sep
(3) |
Oct
|
Nov
(4) |
Dec
|
2010 |
Jan
(36) |
Feb
(32) |
Mar
(2) |
Apr
(19) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(8) |
Dec
|
2011 |
Jan
(3) |
Feb
|
Mar
(5) |
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(6) |
2012 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(6) |
Dec
(10) |
2014 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(34) |
Aug
(6) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(18) |
Jul
(13) |
Aug
(30) |
Sep
(4) |
Oct
(1) |
Nov
|
Dec
(4) |
2016 |
Jan
(2) |
Feb
(10) |
Mar
(3) |
Apr
|
May
|
Jun
(11) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Karl O. P. <ko...@me...> - 2007-08-05 16:30:08
|
Hi, I'm using sqlgrey 1.6.7 and Postgresql 8.1. Please forgive me if I'm wrong. I've not gone into the code in depth. Like others I'm getting memory leaks, both in the sqlgrey process and the Postgresql process. It almost makes sqlgrey unusable. The suggestion was that there's a problem in the perl dbi prepare_cached call. Research says that there was a problem with a memory leak in perl DBI fixed in 1.51 (IIRC), but I'm running 1.53 so that's not where the problem is. So, I looked at the code. I'm not a perl wiz, but the problem appears to be obvious. Sqlgrey seems to be repeatedly creating prepared queries, each of which differs from the last. The whole point of prepared queries is to have _invariant_ queries, substituted parameters excepted. Here's one example from 1.6.7, there are others: sub is_in_from_awl { my ($self, $sender_name, $sender_domain, $host) = @_; # last_seen less than $self->{sqlgrey}{awl_age} days ago my $sth = $self->prepare("SELECT 1 FROM $from_awl " . 'WHERE sender_name = ? ' . 'AND sender_domain = ? ' . 'AND src = ? ' . 'AND last_seen > ' . $self->past_tstamp($self->{sqlgrey}{awl_age}, 'DAY') ); if (!defined $sth or !$sth->execute($sender_name, $sender_domain, $host)) { The time stamp is going to be different every time. It should be a parameter, just like $sender_name, etc. Like I say, I'm no perl wiz, but it seems to me that this would be sure to cause both the client side (sqlgrey) and server side (Postgresql) to require forever increasing amounts of memory. I'd love to see this fixed. Thanks for the program. Regards, Karl <ko...@me...> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein |
From: Dan F. <da...@ha...> - 2007-08-04 13:41:32
|
Dan Mason wrote: > Under FreeBSD 6 (the professional ISP OS) the shell is nologin. > > sqlgrey:*:1002:1002:Postgrey Owner:/usr/local/share/sqlgrey:/sbin/nologin > > Leave it to Linux to do things wrong. (flame on!) > *nix-religious ppl are funny ;) Bleh. Well.. Many times linux does use /bin/true or /bin/false (which practically does the same thing), but AFAIK makes little difference. The shadowfile contains '!' as password, thus no valid password can be entered. If a valid password COULD be entered, setting /sbin/nologin would do little to save you, as $ su <username> -s /bin/bash would bypass whatever defined in passwd. So i dont see /sbin/nologin hindering anything you cant do another way if you already have so much access that you can define a password for the user. So that said, sure i can make it put in /bin/true or whatever in the .spec file, because it DOES look neater. :) Ill stick it into CVS, but unless someone can convince me otherwise, i dont see it as a problem and wont make a new release based on this alone. - Dan |
From: Chris S. <ch...@cs...> - 2007-08-04 09:47:28
|
On Sat, 4 Aug 2007, Dan Mason wrote: > Leave it to Linux to do things wrong. =A0(flame on!) s/Linux/people/ =2D-=20 Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. =46or more info see: http://en.wikipedia.org/wiki/OpenPGP |
From: John T. <gma...@jt...> - 2007-08-04 01:40:19
|
Dan Mason said the following on 08/03/2007 05:57 PM: <snip> > Under FreeBSD 6 (the professional ISP OS) the shell is nologin. I am using Centos 5 > Leave it to Linux to do things wrong. (flame on!) It seems to a rookie that it is rather cool that two fairly different OS's are able get fairly accurate installs, excepting a, possible, security hole. Further, it seems this hole is pluggable. I wish Mr. Linux would create a clean install for all Linux's (apt-get yum, rpm, deb, etc), whatever works. (flame off!) -- Sincerely, John Thomas |
From: Dan M. <dan...@da...> - 2007-08-04 00:57:16
|
On Fri, Aug 03, 2007 at 05:39:08PM -0700, John Thomas wrote: > I know little and suspect the following would help: > The spec file creates a user that is allowed to login > sqlgrey:x:509:509::/var/sqlgrey:/bin/bash > If possible, wouldn't it be better have the spec file create a user like > this: > sqlgrey:x:509:509::/var/sqlgrey:/sbin/nologin > ? Under FreeBSD 6 (the professional ISP OS) the shell is nologin. sqlgrey:*:1002:1002:Postgrey Owner:/usr/local/share/sqlgrey:/sbin/nologin Leave it to Linux to do things wrong. (flame on!) Dan > John Thomas said the following on 07/21/2007 01:16 PM: > > On Centos 5.0 > > rpmbuild -ta sqlgrey-1.7.5.tar.bz2 > > failed with > > error: Installed (but unpackaged) file(s) found: > > /etc/sqlgrey/discrimination.regexp > > Adding /etc/sqlgrey/discrimination.regexp > > to the %files section of the spec file solved the problem for me. > > > > > -- > Sincerely, > John Thomas > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users -- Daniel R Mason = dan...@da... = Unix Systems Engineer; "Fanatical Islam is not a religion. It is the lust for power and control over other people. It is a destructive, evil force that will sweep away all that is good and fine in this world." -- Orson Scott Card |
From: John T. <gma...@jt...> - 2007-08-04 00:39:16
|
I know little and suspect the following would help: The spec file creates a user that is allowed to login sqlgrey:x:509:509::/var/sqlgrey:/bin/bash If possible, wouldn't it be better have the spec file create a user like this: sqlgrey:x:509:509::/var/sqlgrey:/sbin/nologin ? John Thomas said the following on 07/21/2007 01:16 PM: > On Centos 5.0 > rpmbuild -ta sqlgrey-1.7.5.tar.bz2 > failed with > error: Installed (but unpackaged) file(s) found: > /etc/sqlgrey/discrimination.regexp > Adding /etc/sqlgrey/discrimination.regexp > to the %files section of the spec file solved the problem for me. > -- Sincerely, John Thomas |
From: John T. <gma...@jt...> - 2007-07-21 20:16:08
|
On Centos 5.0 rpmbuild -ta sqlgrey-1.7.5.tar.bz2 failed with error: Installed (but unpackaged) file(s) found: /etc/sqlgrey/discrimination.regexp Adding /etc/sqlgrey/discrimination.regexp to the %files section of the spec file solved the problem for me. -- Sincerely, John Thomas |
From: <as...@ko...> - 2007-07-05 20:38:25
|
Hi. I have been running sqlgrey for a long time on my little home-server - with great success; it is wonderful. Recently I have noticed an annoying increase in memory usage; for instance, right now: $ ps aux | grep [s]qlgrey sqlgrey 26080 0.0 6.6 168832 133220 ? Ss Jun27 0:32 /usr/bin/perl -w /usr/sbin/sqlgrey --daemonize postgres 26113 0.0 17.1 403472 342368 ? S Jun27 0:37 postgres: sqlgrey sqlgrey 127.0.0.1(33636) idle The "only" two changes I have done recently, that I can think of, is upgrading to Debian 4.0 (etch) and migrating to an amd64 machine. The versions I am running are: $ /usr/sbin/sqlgrey --version sqlgrey 1.6.7 $ dpkg -l postgresql-8.1 | grep ^ii ii postgresql-8.1 8.1.9-0etch1 object-relational SQL database, version 8.1 server $ perl -MDBI -e 'print $DBI::VERSION . "\n"' 1.53 $ perl -MDBD::Pg -e 'print $DBD::Pg::VERSION . "\n"' 1.49 $ perl -MNet::Server::Multiplex -e 'print $Net::Server::Multiplex::VERSION . "\n"' 0.94 $ The amount of data in my database is far from overwhelming: 3441 rows in connect, 1497 in from_awl and 47 in domain_awl. A couple of months ago there was a thread about Gentoo/sqlgrey/mysql where the advice was to try different versions of DBI and the DBD driver. I was wondering if anyone is running the same versions as I do with/without problems? I think it would be cool to find the culprit, but before I spend a lot of time trying to track it down, it would be nice to hear if there are other people using the same combination. A quick run through DBI::Changes (1.54-1.58) and Changes for Net::Server::Multiplex (0.95-0.96) did not yield anything immediately obvious, to me. Best regards, Adam -- "Last year I was very tired." Adam Sjøgren as...@ko... |
From: Dan M. <dan...@da...> - 2007-06-22 17:59:53
|
On Fri, Jun 22, 2007 at 06:31:26PM +0200, Dan Faerch wrote: > We briefly discussed SPF a while back, but nobody wanted this bad enough > to actually implement it ;). (Patches are very welcome) Simply using SPF is sort of silly. It'd be nice to have an SPF-whitelist though, where you could say accept anything in the SPF record for google.com. Dan -- Daniel R Mason = dan...@da... = Unix Systems Engineer; "But if the U.S. were to leave and abandon Iraq without establishing the grounds for a united and sovereign country, that would definitely be a second mistake." -- Vladimir Putin |
From: Dan F. <da...@ha...> - 2007-06-22 16:30:40
|
Brent Kennedy wrote: > Bugger! > > Wonder if the developers are looking into domain keys then. > Nope.. Im not, and i havent heard Lionel mention this either, so i doubt it :) We briefly discussed SPF a while back, but nobody wanted this bad enough to actually implement it ;). (Patches are very welcome) Perhaps you can use the whitelisting feature for specific ones like gmail and yahoo ect. Or the discrimination feature from 1.7.5, if you know regular-expressions. BTW. 1.7.4 & 1.7.5 has been running without any problems for over a year on 8 servers here, each handling several million requests daily. So id say its as stable as they come.. Also, 1.7.5 has "one-less-bug(tm)" than 1.6.7. :) - Dan |
From: Michael Z. <zi...@ve...> - 2007-06-22 15:12:21
|
Am Freitag, den 22.06.2007, 09:49 -0400 schrieb Brent Kennedy: > ... is the 1.7.5 devel version stable enough for deployment? Acording to my experience with a medium-sized server (about 30k connects per day) it is. Michael > -- Michael Zimmermann Vegaa Zimmermann Internet Services zi...@ve... http://vegaa.de fon +49 (0)89 6384 9775 fax +49 (0)89 6388 9884 hdy +49 (0)178 785 4945 |
From: Steve H. <st...@th...> - 2007-06-22 14:53:40
|
On Fri, 2007-06-22 at 10:24 -0400, Brent Kennedy wrote: > Bugger! > > Wonder if the developers are looking into domain keys then. > Has anyone implemented DomainKeys using dkfilter ? -- thorNET Internet Services, Consultancy & Training www.thornet.co.uk |
From: Brent K. <b.k...@CH...> - 2007-06-22 14:25:02
|
Bugger! Wonder if the developers are looking into domain keys then. Thanks for the info! -Brent -----Original Message----- From: sql...@li... [mailto:sql...@li...] On Behalf Of Daniel J McDonald Sent: Friday, June 22, 2007 10:19 AM To: SQLgrey users mailing-list Subject: Re: [Sqlgrey-users] SPF Questions On Fri, 2007-06-22 at 09:49 -0400, Brent Kennedy wrote: > The reason I bring this up is that providers like gmail, yahoo, aol > have 2 or 3 dozen mail servers on different networks. Though I don't > want spam, I also don't want to delay their messages. The thought is > that anyone who does SPF gets an automatic bypass. Right, but they don't use spf - they use DomainKeys > -- Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX Austin Energy http://www.austinenergy.com ------------------------------------------------------------------------ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Sqlgrey-users mailing list Sql...@li... https://lists.sourceforge.net/lists/listinfo/sqlgrey-users MessageID: xXYyzb262005qa |
From: Daniel J M. <dan...@au...> - 2007-06-22 14:18:02
|
On Fri, 2007-06-22 at 09:49 -0400, Brent Kennedy wrote: > The reason I bring this up is that providers like gmail, yahoo, aol > have 2 or 3 dozen mail servers on different networks. Though I don't > want spam, I also don't want to delay their messages. The thought is > that anyone who does SPF gets an automatic bypass. Right, but they don't use spf - they use DomainKeys > -- Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX Austin Energy http://www.austinenergy.com |
From: Brent K. <b.k...@CH...> - 2007-06-22 14:03:40
|
I just setup sqlgrey last night on my spam server. I think I have just about every possible way of detecting spam, running on this server now! :P =20 Anyhow, I was looking at the mailing list and looking through the configuration file( btw: using 1.6.7 ), I was unable to find anything useful related to the way SPF is used or handled in the greylisting process. =20 I was hoping to find out if I could use SPF to just bypass the greylist functionality. That way if any domain is setup correctly and has an SPF record, their mail would not be delayed. Now I realize that spam could still come from a domain that had SPF setup, but I was thinking of sqlgrey as more of a first line of defense than a 100% blocking mechanism. =20 The reason I bring this up is that providers like gmail, yahoo, aol have 2 or 3 dozen mail servers on different networks. Though I don't want spam, I also don't want to delay their messages. The thought is that anyone who does SPF gets an automatic bypass. Again, I realize this leaves things wide open for spammers who use SPF, but it does knock out any bots and greatly narrows the list of relay machines that are added to my blacklist. =20 If its not in my version(1.6.7), is the 1.7.5 devel version stable enough for deployment? =20 Thanks! =20 -Brent =20 =20 =20 =20 |
From: Joshua B. <jb...@at...> - 2007-06-18 22:22:12
|
Gotcha, that did it, thanks again On 6/18/07 3:19 PM, "Daniel J McDonald" <dan...@au...> wrote: > On Mon, 2007-06-18 at 15:09 -0700, Joshua Brewer wrote: >> >> >> >> >> >> Jeeze, I feel like an idiot. >> >> >> I've copied the mysql.pm to MySQL.pm, and now something new in the logs: >> >> Jun 19 03:25:00 vps-100_mx1 sqlgrey: fatal: Can't locate object method >> "driver" via package "DBD::MySQL" at >> /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi/DBI.pm line 782. >> Jun 19 03:25:00 vps-100_mx1 sqlgrey: fatal: DBD::MySQL initialisation >> failed: Can't locate object method "driver" via package "DBD::MySQL" at >> /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi/DBI.pm line 782. >> Perhaps the capitalisation of DBD 'MySQL' isn't right. at /usr/sbin/sqlgrey >> line 775 >> >> Does this mean im not crazy? > > your database reference should all be lower case: > > [mcdonalddj@sa ~]$ grep -i mysql /etc/sqlgrey/sqlgrey.conf > # instead of Pg below use "mysql" for MySQL, "SQLite" for SQLite > db_type = mysql > >> >> >> >> >> On 6/18/07 2:27 PM, "Daniel J McDonald" <dan...@au...> >> wrote: >> >>> On Mon, 2007-06-18 at 14:22 -0700, Joshua Brewer wrote: >>>> >>>> >>>> >>>> >>>> Hey guys, I seem to have a problem I was hoping someone could shed some >>>> light on. I am running CentOS 4, and I have installed sqlgrey from the >>>> sqlgrey-1.6.7-1.noarch.rpm. I have installed all the pre-requisites, >>>> however when I go to launch sqlgrey from the init script, I see the >>>> following in my logs: >>>> >>>> >>>> fatal: Can't locate DBD/MySQL.pm in @INC (@INC contains: >>> [...] >>>> /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/DBD/mysql.pm >>>> >>>> >>>> Can anyone offer any suggestions? >>> >>> Case matters. >> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Sqlgrey-users mailing list >> Sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users |
From: Daniel J M. <dan...@au...> - 2007-06-18 22:18:37
|
On Mon, 2007-06-18 at 15:09 -0700, Joshua Brewer wrote: > > > > > > Jeeze, I feel like an idiot. > > > I've copied the mysql.pm to MySQL.pm, and now something new in the logs: > > Jun 19 03:25:00 vps-100_mx1 sqlgrey: fatal: Can't locate object method > "driver" via package "DBD::MySQL" at > /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi/DBI.pm line 782. > Jun 19 03:25:00 vps-100_mx1 sqlgrey: fatal: DBD::MySQL initialisation > failed: Can't locate object method "driver" via package "DBD::MySQL" at > /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi/DBI.pm line 782. > Perhaps the capitalisation of DBD 'MySQL' isn't right. at /usr/sbin/sqlgrey > line 775 > > Does this mean im not crazy? your database reference should all be lower case: [mcdonalddj@sa ~]$ grep -i mysql /etc/sqlgrey/sqlgrey.conf # instead of Pg below use "mysql" for MySQL, "SQLite" for SQLite db_type = mysql > > > > > On 6/18/07 2:27 PM, "Daniel J McDonald" <dan...@au...> > wrote: > > > On Mon, 2007-06-18 at 14:22 -0700, Joshua Brewer wrote: > >> > >> > >> > >> > >> Hey guys, I seem to have a problem I was hoping someone could shed some > >> light on. I am running CentOS 4, and I have installed sqlgrey from the > >> sqlgrey-1.6.7-1.noarch.rpm. I have installed all the pre-requisites, > >> however when I go to launch sqlgrey from the init script, I see the > >> following in my logs: > >> > >> > >> fatal: Can't locate DBD/MySQL.pm in @INC (@INC contains: > > [...] > >> /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/DBD/mysql.pm > >> > >> > >> Can anyone offer any suggestions? > > > > Case matters. > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users |
From: Joshua B. <jb...@at...> - 2007-06-18 22:08:49
|
Jeeze, I feel like an idiot. I've copied the mysql.pm to MySQL.pm, and now something new in the logs: Jun 19 03:25:00 vps-100_mx1 sqlgrey: fatal: Can't locate object method "driver" via package "DBD::MySQL" at /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi/DBI.pm line 782. Jun 19 03:25:00 vps-100_mx1 sqlgrey: fatal: DBD::MySQL initialisation failed: Can't locate object method "driver" via package "DBD::MySQL" at /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi/DBI.pm line 782. Perhaps the capitalisation of DBD 'MySQL' isn't right. at /usr/sbin/sqlgrey line 775 Does this mean im not crazy? On 6/18/07 2:27 PM, "Daniel J McDonald" <dan...@au...> wrote: > On Mon, 2007-06-18 at 14:22 -0700, Joshua Brewer wrote: >> >> >> >> >> Hey guys, I seem to have a problem I was hoping someone could shed some >> light on. I am running CentOS 4, and I have installed sqlgrey from the >> sqlgrey-1.6.7-1.noarch.rpm. I have installed all the pre-requisites, >> however when I go to launch sqlgrey from the init script, I see the >> following in my logs: >> >> >> fatal: Can't locate DBD/MySQL.pm in @INC (@INC contains: > [...] >> /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/DBD/mysql.pm >> >> >> Can anyone offer any suggestions? > > Case matters. |
From: Daniel J M. <dan...@au...> - 2007-06-18 21:26:31
|
On Mon, 2007-06-18 at 14:22 -0700, Joshua Brewer wrote: > > > > > Hey guys, I seem to have a problem I was hoping someone could shed some > light on. I am running CentOS 4, and I have installed sqlgrey from the > sqlgrey-1.6.7-1.noarch.rpm. I have installed all the pre-requisites, > however when I go to launch sqlgrey from the init script, I see the > following in my logs: > > > fatal: Can't locate DBD/MySQL.pm in @INC (@INC contains: [...] > /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/DBD/mysql.pm > > > Can anyone offer any suggestions? Case matters. -- Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX Austin Energy http://www.austinenergy.com |
From: Joshua B. <jb...@at...> - 2007-06-18 21:22:10
|
Hey guys, I seem to have a problem I was hoping someone could shed some light on. I am running CentOS 4, and I have installed sqlgrey from the sqlgrey-1.6.7-1.noarch.rpm. I have installed all the pre-requisites, however when I go to launch sqlgrey from the init script, I see the following in my logs: fatal: Can't locate DBD/MySQL.pm in @INC (@INC contains: /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.4/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.3/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.2/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.1/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.4/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.3/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.2/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.1/x86_64-linux-thread-multi /usr/lib64/p Jun 18 23:34:37 vps-100_mx1 sqlgrey: fatal: install_driver(MySQL) failed: Can't locate DBD/MySQL.pm in @INC (@INC contains: /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib64/perl5/site_perl/5.8.5/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.4/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.3/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.2/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.1/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.4/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.3/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.2/x86_64-linux-thread-multi However, DBD::MySQL is installed, as follows [root@vps-100_mx1 src]# rpm -qi perl-DBD-MySQL-2.9004-3.1.centos4 Name : perl-DBD-MySQL Relocations: (not relocatable) Version : 2.9004 Vendor: CentOS Release : 3.1.centos4 Build Date: Sun May 20 15:06:51 2007 Install Date: Tue Jun 19 00:42:35 2007 Build Host: v20z-x86-64 Group : Applications/Databases Source RPM: perl-DBD-MySQL-2.9004-3.1.centos4.src.rpm Size : 243733 License: distributable Signature : DSA/SHA1, Sun May 20 15:48:02 2007, Key ID a53d0bab443e1821 Packager : Johnny Hughes <jo...@ce...> URL : http://search.cpan.org/search?query=DBD%3A%3AMySQL Summary : A MySQL interface for perl Description : An implementation of DBI for MySQL for Perl. [root@vps-100_mx1 src]# rpm -ql perl-DBD-MySQL-2.9004-3.1.centos4 /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/Bundle/DBD/mysq l.pm /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/DBD/mysql.pm /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/DBD/mysql/GetIn fo.pm /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/DBD/mysql/INSTA LL.pod /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/Mysql.pm /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/Mysql/Statement .pm /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/auto/DBD/mysql/ mysql.bs /usr/lib64/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/auto/DBD/mysql/ mysql.so /usr/share/man/man3/Bundle::DBD::mysql.3pm.gz /usr/share/man/man3/DBD::mysql.3pm.gz /usr/share/man/man3/DBD::mysql::INSTALL.3pm.gz /usr/share/man/man3/Mysql.3pm.gz Can anyone offer any suggestions? -JB |
From: Steven P. M. <st...@bu...> - 2007-06-03 23:28:57
|
First up thank you for the response. I did originally install using portage but based on your information just compiled by source which fixed the issue. Now I'm just having one or two problems with mysql permissions. Hopefully I'll be able to resolve them without additional assistance. I've been using Gentoo for about a year or so and have found it to be a very good distro actually. I completely respect your opinion as there is no perfect distro for everyone, it's usually a comfort level thing. I'm wondering if your dislike of Gentoo is specific to sqlgrey or are you making a general statement about its use? What is your preferred distro for sqlgrey? -----Original Message----- From: sql...@li... [mailto:sql...@li...] On Behalf Of Matteo Niccoli Sent: Sunday, June 03, 2007 5:04 PM To: SQLgrey users mailing-list Subject: Re: [Sqlgrey-users] DBCluster connect issue Steven Pfohl Murphy ha scritto: >"fatal: Can't locate object method "connect" via package "DBIx::DBCluster" >at /usr/sbin/sqlgrey line 833." >I'm using sqlgrey 1.7.5 on a gentoo linux boxen and mysql 5.0.38. Ok, 2 things. 1) Gentoo is sh%t. Switch distro :) 2) There's no way to enable db cluster using ebuild provided from gentoo. If you want use cluster, you have to patch manually the sources, replace use DBI with use DBIx::DBCluster, and install the module manually ( you have to gunzip manually the sources from /usr/portage/distfiles, and take the sources from there). I think you installed sqlgrey from ebuild, right? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Sqlgrey-users mailing list Sql...@li... https://lists.sourceforge.net/lists/listinfo/sqlgrey-users |
From: Matteo N. <mat...@st...> - 2007-06-03 21:02:55
|
Steven Pfohl Murphy ha scritto: >"fatal: Can't locate object method "connect" via package "DBIx::DBCluster" >at /usr/sbin/sqlgrey line 833." >I'm using sqlgrey 1.7.5 on a gentoo linux boxen and mysql 5.0.38. Ok, 2 things. 1) Gentoo is sh%t. Switch distro :) 2) There's no way to enable db cluster using ebuild provided from gentoo. If you want use cluster, you have to patch manually the sources, replace use DBI with use DBIx::DBCluster, and install the module manually ( you have to gunzip manually the sources from /usr/portage/distfiles, and take the sources from there). I think you installed sqlgrey from ebuild, right? |
From: Dan F. <da...@ha...> - 2007-06-02 15:57:11
|
Steven Pfohl Murphy wrote: > "fatal: Can't locate object method "connect" via package "DBIx::DBCluster" > at /usr/sbin/sqlgrey line 833." > > I'm using sqlgrey 1.7.5 on a gentoo linux boxen and mysql 5.0.38 Sounds like DBIx::DBCluster isnt installed correctly.. This should have happened when you did make use_dbcluster Goto where you unzipped the sqlgrey package and do the following (as root): cd lib/DBIx-DBCluster-0.01/ perl Makefile.PL make make install - Dan |
From: Steven P. M. <st...@bu...> - 2007-06-02 15:25:41
|
I'm trying to get DB clustering to work. My servers are all replicating as they should and sqlgrey is configured as it states in the documentation but I'm still getting this error when I go to startup sqlgrey: "fatal: Can't locate object method "connect" via package "DBIx::DBCluster" at /usr/sbin/sqlgrey line 833." I'm using sqlgrey 1.7.5 on a gentoo linux boxen and mysql 5.0.38. Any help or direction is greatly appreciated. Steve |
From: Lionel B. <lio...@bo...> - 2007-05-24 20:27:56
|
McDonald, Dan wrote the following on 24.05.2007 22:01 : > > I've been running sqlgrey 1.6.6 for a while, and am comfortable with how > it works. One of my spam-tossers lost a disk, and I am rebuilding the > system from scratch (It's been in operation basically unchanged for a > year - with this sort of application it's good to get a nice clean slate > now and again). Should I stick with 1.6.6 or go with the latest > experimental release? (1.7.5?) > Currently the experimental has one less known bug than the stable (if syslog dies, SQLgrey can die too). Lionel |