Hi Tony, It looks like you are having a really hard time to get the system working. This REALLY concerns me. Given your quite thorough efforts I'm becoming convinced that you must be hitting some environmental error that's beside our reach. The first thing that comes to mind are the problems some people have been having with a version of the daemon that works in fork mode under Windows. Could you please manually switch the daemon configuration to "threaded" mode retest, and then "forked" and retest ? I'm worried that this might be a DBI or ActiveState Perl issue and I want to make sure you try both these options -- they were developed to address this issue.
The current daemon configuration is probably "auto" which under your Windows configuration must have automatically switched to "threaded", but please try both configurations anyway: http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-19-9/manual/html-single/manual.html#INSTALLATION-INTEGRATION-DAEMON It looks like problems with Bugzilla 2.22 on Windows were reported before by David: http://bugzilla.mkgnu.net/show_bug.cgi?id=912 http://lists.mkgnu.net/pipermail/scmbug-users/2007-March/000852.html David, did you end up trying 0.19.9 at all ? What happened in your case ? Did the upgrade to Bugzilla 2.22.2 help ? Was this a daemon issue that was fixed in 0.19.9 ? On Tue, 2007-04-17 at 15:18 -0600, Day, Tony wrote: > Hello all, > > I've been pulling my hair out for the last two days trying to get this > working and I am stuck. > > I have Subversion 1.4.3 on a Windows Server 2003 machine > I have Bugzilla 2.22.0 on a Windows Server 2003 machine > I am using SCMBug version 0-19-9 > > Try as I might, I cannot get SCMBug to update the bug. It's extremely > hard to debug when all I get in the activity log is: > > Tue Apr 17 14:23:08 2007 XXX.XXX.XXX.XXXX:XXXX Processing connection > from ‰íÐ > Tue Apr 17 14:23:08 2007 XXX.XXX.XXX.XXXX:XXXX Connection from ‰íÐ > processed According to this, the connection went through. I'd recommend you start debugging in the Bugzilla backend in Bugzilla.pm:integration_add_comment to see what goes wrong. > On a sidenote, anyone know why I get weird characters that should be > specifying the server in the log? Yes. http://bugzilla.mkgnu.net/show_bug.cgi?id=264#c35 http://bugzilla.mkgnu.net/show_bug.cgi?id=264#c30 > From what I can tell the glue.conf is okay. I have verified the daemon > location and port are okay. I've tried various log templates to no > avail. My main_trunk_directory is called LAG. While that shouldn't > matter I feel I should mention it as I am not using the 'recommended' > dir name. It should be easy to test a new repository with a main_trunk_directory called 'trunk' though. I doubt this is the problem. Thanks though. > Far as I can tell the daemon config is okay too. I have tried auto > and threaded execution modes. I verified that I correctly input the Could you try both 'forked' and 'threaded' again please ? Are you sure you are restarting the daemon each time ? > bugtracker type,version,location and port. For the port I tried > localhost, 127.0.0.1, and the IP of the machine. No joy. I verified > the database name, username, and password are accurate. I used the > one-to-one mapping for SCM usernames. I know that is right cause if I > put in something SCMBug doesn't like I get an error when trying to > commit to SVN. > > At this point, I really hope I am just overlooking something obvious > and stupid cause I've wasted two days trying to get this running. If > there is any additional information I can provide please let me know. If it's not the forked vs threaded issue, I think you might have to resort to debugging the Bugzilla backend. I know this isn't exactly the answer you were expecting. _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
