Re: trac/wiki is DOWN AGAIN
Marko It is up and in sync now. Shree Karulkar Mac OS Forge skarul...@apple.com Work: 408.783.2992 Mobile: 650.270.7976 On Dec 17, 2014, at 11:56 PM, Marko Käning mk-macpo...@techno.ms wrote: Hi Shree, trac and wiki aren’t responding anymore! Regards, Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #46099: Snow Leopard builder builds using System cc (was: pango @1.38.0_1 +universal: builds using System cc, fails to lipo)
This is what I see.
tensix-slave:~ local$ xcodebuild -version
Xcode 3.2.6
Component versions: DevToolsCore-1809.0; DevToolsSupport-1806.0
BuildVersion: 10M2518
tensix-slave:~ local$
Shree Karulkar
Mac OS Forge
skarul...@apple.com
Work: 408.783.2992
Mobile: 650.270.7976
On Dec 3, 2014, at 2:43 AM, MacPorts nore...@macports.org wrote:
#46099: Snow Leopard builder builds using System cc
-+-
Reporter: ryandesign@…| Owner: admin@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: server/hosting |Version:
Resolution: | Keywords:
Port: |
-+-
Changes (by ryandesign@…):
* owner: macports-tickets@… = admin@…
* version: 2.3.3 =
* component: ports = server/hosting
* port: pango =
Comment:
Works fine on my Snow Leopard machine.
Another port, [https://build.macports.org/builders/buildports-snowleopard-
x86_64/builds/31869/steps/compile/logs/stdio tbb, is also building with
System cc] on the Snow Leopard builder for now readily apparent reason.
I see another build with these messages:
{{{
Building pcre (1 of 3)...Warning: xcodebuild exists but failed to execute
package found, not building again
Building mpvim (2 of 3)...Warning: xcodebuild exists but failed to execute
package found, not building again
Building cyrus-sasl2 (3 of 3)...Warning: xcodebuild exists but failed to
execute
package found, not building again
}}}
Shree, can you check what `xcodebuild -version` is showing on the Snow
Leopard builder? Xcode 3.2.6 may need to be reinstalled on it.
--
Ticket URL: https://trac.macports.org/ticket/46099#comment:2
MacPorts https://www.macports.org/
Ports system for OS X
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac down?
Is its up now and in sync. Shree Karulkar Mac OS Forge skarul...@apple.com Work: 408.783.2992 Mobile: 650.270.7976 On Nov 19, 2014, at 3:35 AM, Rainer Müller rai...@macports.org wrote: Yes, trac.macports.org does not respond at the moment. Shree, could you please take a look? Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac down?
Should be good now. Shree Karulkar Mac OS Forge skarul...@apple.com Work: 408.783.2992 Mobile: 650.270.7976 On Nov 19, 2014, at 9:37 AM, Brandon Allbery allber...@gmail.com wrote: On Wed, Nov 19, 2014 at 5:32 PM, petr 9...@ingv.it mailto:9...@ingv.it wrote: It worked, but it seems to be down again. Ore is it only me? Not loading for me either. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com mailto:allber...@gmail.com ballb...@sinenomine.net mailto:ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net http://sinenomine.net/ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Trac unresponsive (eom)
It is back up now and in sync. Shree Karulkar Mac OS Forge skarul...@apple.com Work: 408.783.2992 Mobile: 650.270.7976 On Nov 8, 2014, at 8:43 PM, Lawrence Velázquez lar...@macports.org wrote: ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Trac is down
Sure thing, thanks. It is back up now and in sync with svn. Let me know if you see any issues. Shree Karulkar Mac OS Forge skarul...@apple.com Work: 408.783.2992 Mobile: 650.270.7976 On Oct 20, 2014, at 4:08 PM, Lawrence Velázquez lar...@macports.org wrote: Hi Shree, Trac seems to be down. Could you take a look? Thanks. vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Captcha Error !
I see a text called toilet could that be matching the badcontent page?
Shree
Sent from my iPhone
On Oct 11, 2014, at 6:02 AM, petr 9...@ingv.it wrote:
On 11 Oct 2014, at 12:32, petr 9...@ingv.it wrote:
Hi all,
I get capture errors, when trying to submit a new ticket. Any idea what
could be going on?
~petr
Okay, I now understand what is going on here. Instead of compiling the whole
ticket at once, I subsequently completed it. The ticket is the following:
#45339.
The problem seems to be a too long list of ports in the port field.
This is what I tried to include:
{{{
astyle-dev bzflag CrimsonFields ditaa duke3d GetPoints gobby gource
HideSysFiles hub iTunesMatchHelper libcaca libinfinity macportsscripts MyLoss
objectmarker offlinefs org-mode-devel PRICE-aqua prolog-mode.el py-apsw
py-blist py-clint py-crcmod py-docx py-futures py-irclib py-libgmail py-metar
py-pydot py-pyttsx py-pyx py-sip py-tweepy py-url py-urlwatch py-urwid
py-w3lib qwt rgm3800 rgm3800py rocksndiamonds rott ShiftIt sqlitedbrowser
supertuxkart tex-beamerposter tex-f7u12 tex-gantt tex-songs tex-whizzytex
toilet
}}}
The length is 522 characters. Might it be that the limit is something like
500 chars, or even 512?
I just tested, length is not the issue!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac down?
It is up now. Let me know if you see any issues. -Shree On Sep 5, 2014, at 2:58 PM, Marko Käning mk-macpo...@techno.ms wrote: Hi Shree, I can’t seem to get response from trac… Greets, Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mavericks MacPorts Base Buildbot is hanging in svn
Clemens Didn’t see anything odd so I restarted it. Let me know if it hangs again. -Shree On Aug 19, 2014, at 5:10 PM, Clemens Lang c...@macports.org wrote: Hi, it seems the Mavericks base builbot locks up while trying to check out an SVN working copy. It currently hangs: https://build.macports.org/builders/buildbase-mavericks-x86_64/builds/460/steps/svn/logs/stdio and will eventually time out as it has before: https://build.macports.org/builders/buildbase-mavericks-x86_64/builds/458/steps/svn/logs/stdio The error message will be svn: E175002: REPORT of '/repository/macports/!svn/vcc/default': Could not read response body: Secure connection truncated (https://svn.macports.org), which looks like a network issue to me. Can you take a look? -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: qt5-mac: parallel build?
Looking into it, sometimes this happens if they are in the middle of an update. Shree On Jun 30, 2014, at 2:26 PM, Clemens Lang c...@macports.org wrote: Hi Shree, Are the buildbots even working? I'm getting The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. ever since I wanted to check whether the Qt build was successful. Mojca Can you take a look? I've noticed the same behavior last weekend. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac is down (eom)
Trac is up now. -Shree On May 28, 2014, at 5:44 AM, Christoph Iserlohn ciserl...@macports.org wrote: ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac down?
All Trac is up again. Shree On May 20, 2014, at 3:24 AM, Ryan Schmidt ryandes...@macports.org wrote: On May 20, 2014, at 05:19, Peter Danecek peter.dane...@bo.ingv.it wrote: I have problems to contact trac and http://www.downforeveryoneorjustme.com/trac.macports.org indicates that this is not only a local problem. Can someone look into this? I've forwarded your message to admin at macosforge dot org; they're the ones who can address infrastructure issues. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Trac is down
It is up again. Shree On May 16, 2014, at 12:29 PM, Shreeraj Karulkar skarul...@apple.com wrote: Looking into it, too many httpd, bogged down Shree On May 16, 2014, at 12:25 PM, Mojca Miklavec mo...@macports.org wrote: Hi, Trac seem to be offline. Mojca ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Snow Leopard buildbot out of disk space
I think I'll just increase the disk size. I'll do it a little later today will need a reboot. Shree Sent from my iPhone On May 2, 2014, at 6:06 AM, Christoph Iserlohn ciserl...@macports.org wrote: See https://build.macports.org/builders/buildports-snowleopard-x86_64/builds/26132/steps/compile/logs/stdio -- Christoph ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac is currently having a problem: adding comments isn't possible
Marko I just added a comment to the ticket. Are you logged in as m...@macports.org? Shree On May 2, 2014, at 11:36 AM, mk-macpo...@techno.ms wrote: Hi Shree, when I tried to add a comment to a ticket [1] I just got the response “Trac Error” from MacPorts trac. Since this happened a couple of times within the last 2 hrs or so I guess something is wrong on the server side, because switching to another web client didn’t help either. Greets, Marko [1] https://trac.macports.org/ticket/43539#trac-add-comment ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: trac is currently having a problem: adding comments isn't possible
Is anyone else having a similar problem ? Marko I know this sounds basic but can you try flushing the cache, cookies etc? Shree Sent from my iPhone On May 2, 2014, at 12:01 PM, mk-macpo...@techno.ms wrote: Hmmm, you could add a comment? I see you could... Well, yes, I was logged on with my handle. Used Safari and Firefox and both gave and still give me this error! Greets, Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Buildbots offline?
It is back up right now. Shree On Apr 27, 2014, at 5:41 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Begin forwarded message: From: Craig Treleaven ctrelea...@cogeco.ca Subject: Buildbots offline? Date: April 27, 2014 at 20:40:09 EDT To: macports-dev@lists.macosforge.org For about 24 hours, I get a 503 Service Temporarily Unavailable message trying to access https://build.macports.org/ Craig ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate
Clemens Thanks for your patience, I’ll get that squared soon. Shree On Apr 24, 2014, at 10:02 AM, Clemens Lang c...@macports.org wrote: Hi, Alright that gives me something to chew on. Thanks again. The Mavericks base buildslave seems fine now, apparently the working copy was still locked earlier, but a switch to a branch seems to have fixed that. Still persisting are - website not being updated from SVN, and - distfile mirroring not working Thanks for looking into this, Shree. It's very much appreciated. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate
The ticket for ping is still not resolved by the network team. I’ll check to
see if they are resolved any tickets related to the rsync.
Shree
On Apr 24, 2014, at 2:06 PM, Clemens Lang c...@macports.org wrote:
Hi
Thanks for your patience, I’ll get that squared soon.
Just as an update, it seems the distfile mirroring is working again as
of yesterday night. A few new distfiles popped up with dates similar to
23-Apr-2014 07:38 (example is wireshark 1.10.7)
so thank you for that.
MacPorts will still not use the MacOSForge mirrors, because they don't
repsond to ICMP ping requests. See http://trac.macports.org/ticket/43345.
The affected machines would be 17.251.224.21{7,8}.
The website update issue isn't fixed yet (just in case you had already
been working on that and needed a commit to test).
Thanks for fixing the distfiles problems :-)
--
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mavericks buildslave seems to be stuck
Rebooting please standby. Shree On Apr 22, 2014, at 5:22 PM, Joshua Root j...@macports.org wrote: It's been working on py-graph-tool for over 26 hours. https://build.macports.org/builders/buildports-mavericks-x86_64/builds/3062 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mavericks buildslave seems to be stuck
Server is back up now and seems to be building. Let me know if you still see any issues. Shree On Apr 22, 2014, at 5:46 PM, Shreeraj Karulkar skarul...@apple.com wrote: Rebooting please standby. Shree On Apr 22, 2014, at 5:22 PM, Joshua Root j...@macports.org wrote: It's been working on py-graph-tool for over 26 hours. https://build.macports.org/builders/buildports-mavericks-x86_64/builds/3062 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate
All Just wanted to let you know that I haven’t forgotten about this. On the build base issue, I have tried the same command that has worked on others and also su to buildbot and tried to run from there. Each time I get the expected reply back so it has the new cert but there is still a problem. I will continue working on it soon as I catchup on a couple of things that happened while I was gone. Shree On Apr 21, 2014, at 9:19 AM, Clemens Lang c...@macports.org wrote: Hi, On 2014-4-21 15:46 , Shreeraj Karulkar wrote: [2,3,4] Lion seems to have an non svn error now, Mavericks is still building will keep a watch. And Mtn Lion is now okay. Yeah, Lion is now failing the trace mode test. That's actually expected at the moment. I cannot look into that because I don't have a Lion machine and wanted to ask on the list whether somebody can run the test and provide the output – I just wanted to make sure it was reproducible first, which I couldn't because of the buildbot problems. So that's nothing to worry about at the moment. I don't recall the thread on the disk space problems, so that probably was on -mgr, which I don't read, but I see Joshua and Ryan already answered those questions. Re the website update problem, that's not fixed. If I remember correctly that used to happened instantly, so that would mean it's a post-commit hook, not a cronjob. I just committed https://trac.macports.org/changeset/119248 but it didn't show up in https://www.macports.org/macports.css where I expected it to be. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate
Clemens I seem to be missing the most obvious. I looked extensively for the post-commit hooks for macports.css and realized that the file on the server has a date stamp from Apr 2013. You can see it in the log as well — https://www.macports.org/macports.css Can anyone confirm if it has worked after that date? Was it taken off around that time? Mavericks is still not co-operating. Shree On Apr 21, 2014, at 9:19 AM, Clemens Lang c...@macports.org wrote: Hi, On 2014-4-21 15:46 , Shreeraj Karulkar wrote: [2,3,4] Lion seems to have an non svn error now, Mavericks is still building will keep a watch. And Mtn Lion is now okay. Yeah, Lion is now failing the trace mode test. That's actually expected at the moment. I cannot look into that because I don't have a Lion machine and wanted to ask on the list whether somebody can run the test and provide the output – I just wanted to make sure it was reproducible first, which I couldn't because of the buildbot problems. So that's nothing to worry about at the moment. I don't recall the thread on the disk space problems, so that probably was on -mgr, which I don't read, but I see Joshua and Ryan already answered those questions. Re the website update problem, that's not fixed. If I remember correctly that used to happened instantly, so that would mean it's a post-commit hook, not a cronjob. I just committed https://trac.macports.org/changeset/119248 but it didn't show up in https://www.macports.org/macports.css where I expected it to be. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate
Alright that gives me something to chew on. Thanks again. Shree Sent from my iPhone On Apr 21, 2014, at 6:24 PM, Ryan Schmidt ryandes...@macports.org wrote: On Apr 21, 2014, at 18:59, Shreeraj Karulkar wrote: I seem to be missing the most obvious. I looked extensively for the post-commit hooks for macports.css and realized that the file on the server has a date stamp from Apr 2013. You can see it in the log as well — https://www.macports.org/macports.css Can anyone confirm if it has worked after that date? Was it taken off around that time? Correct, April 2013 is the last time, prior to today, that macports.css was modified: https://trac.macports.org/log/trunk/www/macports.css However other files that make up the web site have been modified since then: https://trac.macports.org/log/trunk/www You could look in the www folder (and all subfolders) for the most-recently-modified file, to see the last time the hook was working, if that helps you diagnose the problem. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts website and distfiles not updating, buildbots don't accept SSL certificate
Clemens Was out on vacation and will update you on everything soon. However there maybe a few things already fixed. [1] I did a see a few cron failures earlier today but they seem to have fixed. Can you confirm again. [2,3,4] Lion seems to have an non svn error now, Mavericks is still building will keep a watch. And Mtn Lion is now okay. [5,6] In the last email chain I had mentioned that the ../var/macports/software directory was about 24 G when it should’ve been about 8 to 9 G. But I haven’t heard if I need to delete any files there, if so which ones? I’ll look into the mirroring issue tomorrow. If there is anything else that needs my attention please feel free to ping me. Shree On Apr 20, 2014, at 1:48 AM, Clemens Lang c...@macports.org wrote: Hi could you please look into the following issues that are still persisting with MacPorts' infrastructure at MacOSForge when you have some time? First, the MacPorts website isn't being updated from the SVN after a commit. This used to happen instantly, so I assume it should be defined somewhere in a post-commit hook. For example, I just committed [1], which should now be visible in the source of the page served at macports.org, but it isn't. Second, the Lion, Mountain Lion and Mavericks buildbots don't accept the SVN's SSL certificate: [2,3,4]. If I remember correctly, the command to run was sudo -u buildbot env HOME=/buildbot/base-slave svn info https://svn.macports.org/repository/macports/trunk/base See also [5]. It also seems the SL buildbot is out of disk space (again?), see [6]. Last but not least, new distfiles are still not being mirrored. I assume there is a cronjob that should download them to distfiles.macports.org that no longer works. Thanks for looking into this. [1] https://trac.macports.org/changeset/119201 [2] https://build.macports.org/builders/buildbase-lion-x86_64/builds/947/steps/svn/logs/stdio [3] https://build.macports.org/builders/buildbase-mtln-x86_64/builds/734/steps/svn/logs/stdio [4] https://build.macports.org/builders/buildbase-mavericks-x86_64/builds/224/steps/svn/logs/stdio [5] https://trac.macports.org/ticket/42727 [6] https://trac.macports.org/ticket/43411#comment:5 -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git.macports.org not syncing since 11 March
Finally git-push ran successfully. Can you please take a look and let me know if you see issues? Sorry for the delay. Shree On Apr 4, 2014, at 9:37 AM, Mark Anderson e...@emer.net wrote: Yeah, I continue to get up-to-date on my git pull upstream masters. I could have sworn more work was going on. Mark —Mark ___ Mark E. Anderson e...@emer.net On Fri, Apr 4, 2014 at 3:51 AM, Rainer Müller rai...@macports.org wrote: On 2014-04-03 21:24, Shreeraj Karulkar wrote: I have changed it. THanks for brining this up. Hm, but the git mirror is still not updating. The latest commit synced was r117767 on March 11. Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git.macports.org not syncing since 11 March
That is odd, we have one Firewall Rule from the Internet to git.macports.org for git and it was tested successfully. Can anyone run the following command and send me the output. Needs to be done without VPN to any of our internal networks. $ telnet git.macports.org 9418 Shree On Apr 2, 2014, at 8:48 AM, William Siegrist wsiegr...@apple.com wrote: Shree? -Bill On Apr 2, 2014, at 7:41 AM, David Röthlisberger da...@rothlis.net wrote: FYI the git mirror at git.macports.org isn't syncing with the svn repository since 11 March. There's a 9-day-old ticket with no activity at https://trac.macports.org/ticket/43058 The last commit is: http://svn.macports.org/repository/macports/trunk@117767 Cheers, Dave. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git.macports.org not syncing since 11 March
Clemens You are right there doesn’t seem to be anything wrong with the access from the internet, and I have checked that the internal access to git.macports.org is also okay. I even restarted the cron daemon but it still shows the latest update on git.macports of March 11. I’ll looking but running out of ideas. Shree On Apr 2, 2014, at 9:25 AM, Clemens Lang c...@macports.org wrote: Hi Shree That is odd, we have one Firewall Rule from the Internet to git.macports.org for git and it was tested successfully. I don't think Internet - git.macports.org is the problem, but rather (1) there's something wrong with the post-commit hook or cronjob updating the Git mirror (2) there's a network problem from that server to git.macports.org. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Josh I suppose this is not working yet? Although there is a freeze they updated the notes that traffic is not blocked.For where it is failing is it possible to get a traceroute output from the internet to any of the servers in question here ? IST are asking for this info to troubleshoot this furthur. Let me know if anyone can and I’ll try to find another way to figure this out. Shree Sent from my iPhone On Mar 28, 2014, at 8:30 AM, Joshua Root j...@macports.org wrote: Any news on this, Shree? - Josh On 2014-3-18 06:43 , Shreeraj Karulkar wrote: 2) Ping issue: I have reopened the ticket which IST had resolved earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge - ICMP . Will let you know as soon as I find out. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Josh
The rsync command that is failing is something like this
buildbot@build buildbot]$ grep rsync deploy_archives.sh
rsync -rlDzv --ignore-existing ${ULPATH}/ ${DLHOST}:${DLPATH}
rsync -rlDzv --ignore-existing ${ULPATH}/ ${DLPATH}
[buildbot@build buildbot]$
I need some help in running a strace on it and providing support the out put.
The command will look like.
# strace -f -t -T -o /tmp/rsync-rlDzv.trc rsync -rlDzv --ignore-existing
${ULPATH}/ ${DLHOST}:${DLPATH}
I have done this by using test directory and test files between build.macports
and packages.macports but it did not encounter any errors.
Shree
On Mar 17, 2014, at 11:12 PM, Joshua Root j...@macports.org wrote:
On 2014-3-18 06:43 , Shreeraj Karulkar wrote:
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine you
are probably referring to the deploy_archives.sh is failing for Mavericks
right? I have tried send a file via rsync with similar options (-rlDzv) from
build.macports to rsync.macports and it went through successfully. I also
did a su to user buildbot and sent a test file through successfully. It did
prompt me to accept the RSA key though. Can you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh options
like the --ignore-existing” optionthat is being used in the script. However
the script has not changed 2013 so I am not sure it thats an issue.
I am still working on this and would appreciate any clues from anyone, sorry
for the delay in the resolution of these issues.
There are three buildbot-related issues remaining:
1. buildslaves can't selfupdate (possibly they can't connect to
rsync.macports.org).
https://build.macports.org/builders/buildports-mavericks-x86_64/builds/2211/steps/sync/logs/stdio
2. buildmaster can't connect to packages.macports.org with rsync.
https://build.macports.org/builders/buildports-mavericks-x86_64/builds/2210/steps/deploy%20archives/logs/stdio
3. buildmaster is not receiving any changesets. These should come from
the post-commit hook which presumably runs on svn.macports.org.
- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Josh Thanks for the update and patience. We will get this resolved too soon. Shree Sent from my iPhone On Mar 19, 2014, at 12:06 AM, Joshua Root j...@macports.org wrote: The buildmaster is now receiving changesets, and selfupdate appears to be working on the slaves too. Thanks! The failure to deploy archives to packages.m.o remains. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Buildbot fails to upload packages...
Nope, I am looking into it. Shree On Mar 19, 2014, at 8:56 AM, Eric A. Borisch ebori...@macports.org wrote: Just making sure this hasn't dropped off the radar. Just picking the latest build: https://build.macports.org/builders/buildports-lion-x86_64/builds/18908/steps/deploy%20archives/logs/stdio - Eric ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Ryan 1) MySQL database: I have enabled access from the www.macports server and tested access successfully. Restarted mysqld on the data server and restarted httpd on the www server. I still can’t get to https://www.macports.org/ports.php. There is something missing that I can’t figure out. 2) Ping issue: I have reopened the ticket which IST had resolved earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge - ICMP . Will let you know as soon as I find out. 3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine you are probably referring to the deploy_archives.sh is failing for Mavericks right? I have tried send a file via rsync with similar options (-rlDzv) from build.macports to rsync.macports and it went through successfully. I also did a su to user buildbot and sent a test file through successfully. It did prompt me to accept the RSA key though. Can you check if it has worked? There is also a reference to use -e in the rsync options to pass ssh options like the --ignore-existing” optionthat is being used in the script. However the script has not changed 2013 so I am not sure it thats an issue. I am still working on this and would appreciate any clues from anyone, sorry for the delay in the resolution of these issues. Shree On Mar 17, 2014, at 5:58 AM, Ryan Schmidt ryandes...@macports.org wrote: Could we get a status update on these remaining migration issues: * MySQL database for web site offline or inaccessible * Online http servers not responding to pings * Buildbot/buildslaves not working Thanks. -Ryan On Mar 15, 2014, at 06:10, Ryan Schmidt ryandes...@macports.org wrote: Thanks. The two pages are now responding without the 21-second delay, but still say the database is offline. Also, we still have no responses to pings to distfiles.macports.org and packages.macports.org (though web services are functioning correctly). On Mar 14, 2014, at 01:46, Shreeraj Karulkar skarul...@apple.com wrote: Ryan I have put a request for the MySQL ports. We missed those while focusing on PSQL ports. We should be good by tomorrow evening. Shree Sent from my iPhone On Mar 13, 2014, at 11:14 PM, Ryan Schmidt ryandes...@macports.org wrote: Shree: A gentle reminder: Another outstanding issue for us is the MySQL database on the web site. It feeds the ports page at: https://www.macports.org/ports.php The database server is either not running or is not accessible to the web server, so the ports page displays only the message “Our database is currently unavailable. We hope to have it back soon!” It also waits 21 seconds before displaying that message, suggesting some kind of network timeout. The database is also queried on the homepage to display the total number of ports in the database: https://www.macports.org/ This too takes 21 seconds before giving up and finally loading the page without the count. If getting the MySQL database back online will take some time, I can modify the homepage to remove the database connection to at least get our homepage displaying speedily again. Note that work was already done to convert the MySQL database to PostgreSQL, as Bill had hinted we should do some time ago: https://trac.macports.org/ticket/40579 I have also done some thus-far unpublished work in this area and would be happy to help with getting this online, if this would be easier than getting the old MySQL server running again. -Ryan ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Ryan MySQL is not running on www.macports.org. There is no startup file in the /etc/ini.d/ and that is something that was not changed as a part of migration. I also did not see an entry for local host in /var/www/html/includes/common.inc”, but then it might be another file. MySQL runs on data.macports.org and www.macports is able to connect to it at port 3306. Shree On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote: Shree, thanks for your reply: On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote: 1) MySQL database: I have enabled access from the www.macports server and tested access successfully. Restarted mysqld on the data server and restarted httpd on the www server. I still can’t get to https://www.macports.org/ports.php. There is something missing that I can’t figure out. The web site is trying to connect to a MySQL server running on localhost (i.e. running on the same machine serving www.macports.org). Is the MySQL server now running on a different server? If so, we need to plug its address into the includes/common.inc file. 2) Ping issue: I have reopened the ticket which IST had resolved earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge - ICMP . Will let you know as soon as I find out. 3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine you are probably referring to the deploy_archives.sh is failing for Mavericks right? I have tried send a file via rsync with similar options (-rlDzv) from build.macports to rsync.macports and it went through successfully. I also did a su to user buildbot and sent a test file through successfully. It did prompt me to accept the RSA key though. Can you check if it has worked? There is also a reference to use -e in the rsync options to pass ssh options like the --ignore-existing” optionthat is being used in the script. However the script has not changed 2013 so I am not sure it thats an issue. I meant that when I look at: https://build.macports.org/console the last revision it shows is r117767, whereas the last revision in the repository right now is r117968. So it hasn’t tried to build any of the 200 most recent revisions. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Ryan
I am a little confused, what is the complete path of the file you have listed
below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on the
server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to it
at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server and
tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the MySQL
server now running on a different server? If so, we need to plug its
address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved earlier.
exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge - ICMP .
Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine
you are probably referring to the deploy_archives.sh is failing for
Mavericks right? I have tried send a file via rsync with similar options
(-rlDzv) from build.macports to rsync.macports and it went through
successfully. I also did a su to user buildbot and sent a test file
through successfully. It did prompt me to accept the RSA key though. Can
you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it thats
an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the 200
most recent revisions.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [macosforge-leaders] Mac OS Forge Migration update
Can’t hellp thinking there must be some place referencing the old IP of
data.macports.org?
Shree
On Mar 17, 2014, at 2:15 PM, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have listed
below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on the
server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to it
at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server and
tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the MySQL
server now running on a different server? If so, we need to plug its
address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved
earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge -
ICMP . Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine
you are probably referring to the deploy_archives.sh is failing for
Mavericks right? I have tried send a file via rsync with similar options
(-rlDzv) from build.macports to rsync.macports and it went through
successfully. I also did a su to user buildbot and sent a test file
through successfully. It did prompt me to accept the RSA key though. Can
you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it thats
an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the
200 most recent revisions.
___
macosforge-leaders mailing list
macosforge-lead...@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macosforge-leaders
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Ryan
Diff of which changes? Not sure what I should be sending you? The one thing I
have done is change its IP address, update the ldap-client (which I am having
some issues with but should not be related) and move the VM it to a new VLAN.
Shree
On Mar 17, 2014, at 2:53 PM, Ryan Schmidt ryandes...@macports.org wrote:
I see, so the file differs from what’s in our repository. Are there any other
uncommitted changes? Having uncommitted changes in the working copy on the
server would cause conflicts if we committed changes to similar lines of the
file. We should commit those changes to the repository so there are no
surprises. Since I don’t think you have commit access, if you want to send a
diff of all the changes I can commit them.
And since the connection parameters seem to be what they should be, we still
don’t know why it’s not connecting. I don’t see any commands in the file to
cause anything to be logged to the web server logfiles. I could try to add
that, so that we could see what the error actually is, but that would
probably log a lot of stuff, since it would log once per hit, and the
MacPorts web site probably gets a lot of hits.
On Mar 17, 2014, at 16:15, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have
listed below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on the
server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to it
at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server
and tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the MySQL
server now running on a different server? If so, we need to plug its
address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved
earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge -
ICMP . Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling fine
you are probably referring to the deploy_archives.sh is failing for
Mavericks right? I have tried send a file via rsync with similar options
(-rlDzv) from build.macports to rsync.macports and it went through
successfully. I also did a su to user buildbot and sent a test file
through successfully. It did prompt me to accept the RSA key though. Can
you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it
thats an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the
200 most recent revisions.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [macosforge-leaders] Mac OS Forge Migration update
I did get hit by one host with the /etc/hosts hardcoding, so I’ve even more
vigilant now.
[root@www /]# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost.localdomain localhost4
localhost4.localdomain4 localhost www
::1 localhost.localdomain localhost.localdomain localhost6
localhost6.localdomain6 localhost www
[root@www /]# uname -n
www.macports.org
[root@www /]#
===
On Mar 17, 2014, at 3:02 PM, Ryan Schmidt ryandes...@macports.org wrote:
Hardcoded in /etc/hosts for some reason?
On Mar 17, 2014, at 16:47, Shreeraj Karulkar skarul...@apple.com wrote:
Can’t hellp thinking there must be some place referencing the old IP of
data.macports.org?
Shree
On Mar 17, 2014, at 2:15 PM, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have
listed below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on
the server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in the
/etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to
it at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server
and tested access successfully. Restarted mysqld on the data server and
restarted httpd on the www server. I still can’t get to
https://www.macports.org/ports.php. There is something missing that I
can’t figure out.
The web site is trying to connect to a MySQL server running on localhost
(i.e. running on the same machine serving www.macports.org). Is the
MySQL server now running on a different server? If so, we need to plug
its address into the includes/common.inc file.
2) Ping issue: I have reopened the ticket which IST had resolved
earlier. exp2://Ticket/18419273 3/17 FireWall Rules for Mac OS Forge
- ICMP . Will let you know as soon as I find out.
3) Buildbot/Slaves: While all the build-slaves seem to be compiling
fine you are probably referring to the deploy_archives.sh is failing
for Mavericks right? I have tried send a file via rsync with similar
options (-rlDzv) from build.macports to rsync.macports and it went
through successfully. I also did a su to user buildbot and sent a test
file through successfully. It did prompt me to accept the RSA key
though. Can you check if it has worked?
There is also a reference to use -e in the rsync options to pass ssh
options like the --ignore-existing” optionthat is being used in the
script. However the script has not changed 2013 so I am not sure it
thats an issue.
I meant that when I look at:
https://build.macports.org/console
the last revision it shows is r117767, whereas the last revision in the
repository right now is r117968. So it hasn’t tried to build any of the
200 most recent revisions.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
If its not this please let me know, I’ll be more than happy to give you more
info.
—
[root@www includes]# pwd
/var/www/html/includes
[root@www includes]# ls
AcceptAbstract.class.php AcceptEncoding.class.php AcceptMime.class.php
footer.inc warnings.inc
AcceptCharset.class.php AcceptLanguage.class.php common.inc
header.inc
[root@www includes]# svn diff common.inc
Index: common.inc
===
--- common.inc (revision 114267)
+++ common.inc (working copy)
@@ -34,10 +34,10 @@
#
# Ports database connection parameters:
-$portsdb_host = 'localhost';
+$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
-$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
+$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
[root@www includes]#
On Mar 17, 2014, at 3:06 PM, Ryan Schmidt ryandes...@macports.org wrote:
In the Subversion repository, our common.inc says the host is localhost:
http://trac.macports.org/browser/trunk/www/includes/common.inc#L34
On the actual web server, you’ve told me common.inc says the host is
data.macports.org. There should not be any differences between the files in
the repository and the files on the web server, so I’m hoping you can run
“svn diff” in the www folder on the web server and send me the result so that
I can commit it to the repository so that there won’t be any differences
anymore.
On Mar 17, 2014, at 17:02, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
Diff of which changes? Not sure what I should be sending you? The one thing
I have done is change its IP address, update the ldap-client (which I am
having some issues with but should not be related) and move the VM it to a
new VLAN.
Shree
On Mar 17, 2014, at 2:53 PM, Ryan Schmidt ryandes...@macports.org wrote:
I see, so the file differs from what’s in our repository. Are there any
other uncommitted changes? Having uncommitted changes in the working copy
on the server would cause conflicts if we committed changes to similar
lines of the file. We should commit those changes to the repository so
there are no surprises. Since I don’t think you have commit access, if you
want to send a diff of all the changes I can commit them.
And since the connection parameters seem to be what they should be, we
still don’t know why it’s not connecting. I don’t see any commands in the
file to cause anything to be logged to the web server logfiles. I could try
to add that, so that we could see what the error actually is, but that
would probably log a lot of stuff, since it would log once per hit, and the
MacPorts web site probably gets a lot of hits.
On Mar 17, 2014, at 16:15, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
I am a little confused, what is the complete path of the file you have
listed below. Below is what I see on the server:file
www.macports.org:/var/www/html/includes/common.inc
#
# Ports database connection parameters:
$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
On Mar 17, 2014, at 2:05 PM, Ryan Schmidt ryandes...@macports.org wrote:
includes/common.inc in the repository says:
# Ports database connection parameters:
$portsdb_host = 'localhost';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
It’s been connecting to localhost at least since r28377 (in 2007).
I can change it to data.macports.org…
Or does it say something different than localhost in the copy that’s on
the server?
On Mar 17, 2014, at 15:58, Shreeraj Karulkar skarul...@apple.com wrote:
Ryan
MySQL is not running on www.macports.org. There is no startup file in
the /etc/ini.d/ and that is something that was not changed as a part of
migration. I also did not see an entry for local host in
/var/www/html/includes/common.inc”, but then it might be another file.
MySQL runs on data.macports.org and www.macports is able to connect to
it at port 3306.
Shree
On Mar 17, 2014, at 1:35 PM, Ryan Schmidt ryandes...@macports.org
wrote:
Shree, thanks for your reply:
On Mar 17, 2014, at 14:43, Shreeraj Karulkar wrote:
1) MySQL database: I have enabled access from the www.macports server
and tested access successfully. Restarted mysqld on the data server
and restarted httpd on the www server. I still can’t get
Re: Mac OS Forge Migration update
The only file that I usually change as part of network changes is the .conf
file inside the /etc/httpd/conf.d/ directory which usually is not a svn file.
In this case I didn’t not even have to change that since it had no IP
references inside it. I am not aware of any other changes.
[root@www conf.d]# ls -ld /etc/httpd/conf.d/www.macports.org.conf
-rw-r--r--. 1 root root 8783 Mar 3 14:57
/etc/httpd/conf.d/www.macports.org.conf
[root@www conf.d]# svn diff /etc/httpd/conf.d/www.macports.org.conf
svn: '/etc/httpd/conf.d/www.macports.org.conf' is not a working copy
[root@www conf.d]#
Shree
On Mar 17, 2014, at 4:18 PM, Ryan Schmidt ryandes...@macports.org wrote:
Ok, I’ve committed that in r117979
Are there any other changes, i.e. outside of the includes directory?
On Mar 17, 2014, at 17:13, Shreeraj Karulkar skarul...@apple.com wrote:
If its not this please let me know, I’ll be more than happy to give you more
info.
—
[root@www includes]# pwd
/var/www/html/includes
[root@www includes]# ls
AcceptAbstract.class.php AcceptEncoding.class.php AcceptMime.class.php
footer.inc warnings.inc
AcceptCharset.class.php AcceptLanguage.class.php common.inc
header.inc
[root@www includes]# svn diff common.inc
Index: common.inc
===
--- common.inc (revision 114267)
+++ common.inc (working copy)
@@ -34,10 +34,10 @@
#
# Ports database connection parameters:
-$portsdb_host = 'localhost';
+$portsdb_host = 'data.macports.org';
$portsdb_name = 'macports';
$portsdb_user = 'macports';
-$portsdb_passwd =
trim(file_get_contents('/opt/local/share/macports/resources/portmgr/script_data'));
+$portsdb_passwd = trim(file_get_contents('/var/www/script_data'));
##
[root@www includes]#
On Mar 17, 2014, at 3:06 PM, Ryan Schmidt ryandes...@macports.org wrote:
In the Subversion repository, our common.inc says the host is localhost:
http://trac.macports.org/browser/trunk/www/includes/common.inc#L34
On the actual web server, you’ve told me common.inc says the host is
data.macports.org. There should not be any differences between the files in
the repository and the files on the web server, so I’m hoping you can run
“svn diff” in the www folder on the web server and send me the result so
that I can commit it to the repository so that there won’t be any
differences anymore.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Ryan I have put a request for the MySQL ports. We missed those while focusing on PSQL ports. We should be good by tomorrow evening. Shree Sent from my iPhone On Mar 13, 2014, at 11:14 PM, Ryan Schmidt ryandes...@macports.org wrote: Shree: A gentle reminder: Another outstanding issue for us is the MySQL database on the web site. It feeds the ports page at: https://www.macports.org/ports.php The database server is either not running or is not accessible to the web server, so the ports page displays only the message “Our database is currently unavailable. We hope to have it back soon!” It also waits 21 seconds before displaying that message, suggesting some kind of network timeout. The database is also queried on the homepage to display the total number of ports in the database: https://www.macports.org/ This too takes 21 seconds before giving up and finally loading the page without the count. If getting the MySQL database back online will take some time, I can modify the homepage to remove the database connection to at least get our homepage displaying speedily again. Note that work was already done to convert the MySQL database to PostgreSQL, as Bill had hinted we should do some time ago: https://trac.macports.org/ticket/40579 I have also done some thus-far unpublished work in this area and would be happy to help with getting this online, if this would be easier than getting the old MySQL server running again. -Ryan On Mar 13, 2014, at 18:08, Shreeraj Karulkar skarul...@apple.com wrote: Hello All Following issues are still pending. 1. data.macports.org has been inaccessible since yesterday 03/12/2014 around 7.30 PM or so when Ryan Schmidt first reported failure on trac.macports. Apparently a change was put in yesterday while took the entire Macports Internal VLAN off limits. A ticket was opened last night and and they are supposed to fix it this evening around 7 PM PST. exp2://Ticket/18428970 DC Network Internal: VLAN connectivity to Mac OS Forge servers 2. Build-slaves could not be moved to the new VLAN due to lack of resources on the Xerves and and request as been put to open ports on the old VLAN. The original ETA was for tomorrow 3/14/2014 but I just checked that they will be doing this tonight as well. exp2://Ticket/18420429 FireWall Rules for Mac OS Forge (Macports Build-Slaves) If you see other issues related to the migration please reply to this email chain. I would appreciate if you can forward this email to people who are not on this list but may need to know. Thanks. Shree ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Mac OS Forge Migration update
Hello All Following issues are still pending. 1. data.macports.org has been inaccessible since yesterday 03/12/2014 around 7.30 PM or so when Ryan Schmidt first reported failure on trac.macports. Apparently a change was put in yesterday while took the entire Macports Internal VLAN off limits. A ticket was opened last night and and they are supposed to fix it this evening around 7 PM PST. exp2://Ticket/18428970 DC Network Internal: VLAN connectivity to Mac OS Forge servers 2. Build-slaves could not be moved to the new VLAN due to lack of resources on the Xerves and and request as been put to open ports on the old VLAN. The original ETA was for tomorrow 3/14/2014 but I just checked that they will be doing this tonight as well. exp2://Ticket/18420429 FireWall Rules for Mac OS Forge (Macports Build-Slaves) If you see other issues related to the migration please reply to this email chain. I would appreciate if you can forward this email to people who are not on this list but may need to know. Thanks. Shree ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Mac OS Forge Migration update
Josh Thanks for confirming, I think we are going to need more additional rules to be requested. Will keep you updated. Shree On Mar 13, 2014, at 10:47 PM, Joshua Root j...@macports.org wrote: MacPorts buildslaves are connecting to the master now, but they still can't connect to rsync.macports.org for selfupdate. The portfiles are synced with svn, so builds are working fine for now, but we will want them to be able to selfupdate when we release a new version of MacPorts base. - Josh On 2014-3-14 10:08 , Shreeraj Karulkar wrote: Hello All Following issues are still pending. 1. data.macports.org has been inaccessible since yesterday 03/12/2014 around 7.30 PM or so when Ryan Schmidt first reported failure on trac.macports. Apparently a change was put in yesterday while took the entire Macports Internal VLAN off limits. A ticket was opened last night and and they are supposed to fix it this evening around 7 PM PST. exp2://Ticket/18428970 DC Network Internal: VLAN connectivity to Mac OS Forge servers 2. Build-slaves could not be moved to the new VLAN due to lack of resources on the Xerves and and request as been put to open ports on the old VLAN. The original ETA was for tomorrow 3/14/2014 but I just checked that they will be doing this tonight as well. exp2://Ticket/18420429 FireWall Rules for Mac OS Forge (Macports Build-Slaves) If you see other issues related to the migration please reply to this email chain. I would appreciate if you can forward this email to people who are not on this list but may need to know. Thanks. Shree ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Scheduled downtime on Mar 11, 15-19 UTC
Bill I just send myself an email from trac.macports.org and it took perhaps a few mins but not super late. Is there anywhere else I can look? Shree On Mar 12, 2014, at 3:22 PM, Clemens Lang c...@macports.org wrote: Hi, When adding new comments to tickets in Trac the page takes a very long time to submit. I can open the same ticket in a different tab and see that the comment has been added, but I haven't seen mails to the -tickets mailing list for the last few comments I added – so I'm guessing the connection to the mail server is running into a timeout. Can you take a look? -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #42727: Server certificate verification failed: issuer is not trusted (https://svn.macports.org
Thanks Ryan. I ran the command on the three slaves and “accepted” the cert
permanently. However, I saw some strange behavior. Not sure if this would be an
issue though.
On teneight-slave” and tennine-slaves the svn info runs fine when used with
a “sudo”, however without sudo (user=local) it keeps prompting to take action
with the new certificates, (reject, accept etc) every time you run the svn info
command.
Let me know what you think.
Shree
On Mar 9, 2014, at 7:53 PM, MacPorts nore...@macports.org wrote:
#42727: Server certificate verification failed: issuer is not trusted
(https://svn.macports.org
-+-
Reporter: ryandesign@…| Owner: wsiegrist@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: server/hosting |Version:
Resolution: | Keywords:
Port: |
-+-
Comment (by ryandesign@…):
I believe you just need to run any svn command on the MacPorts repository
URL, i.e.:
{{{
/usr/bin/svn info https://svn.macports.org/repository/macports
}}}
This will prompt you whether you want to accept the certificate:
{{{
Error validating server certificate for 'https://svn.macports.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: *.macports.org
- Valid: from Mon, 03 Mar 2014 20:37:03 GMT until Mon, 02 Mar 2015
01:19:52 GMT
- Issuer: GlobalSign nv-sa, BE
- Fingerprint:
e6:bd:44:a5:29:e4:ef:ef:47:92:f1:6d:80:e6:48:98:30:30:dc:0b
(R)eject, accept (t)emporarily or accept (p)ermanently?
}}}
Answer p to accept it permanently, and that should be it.
However, I'm not sure which user this task needs to be performed as.
According to the [https://build.macports.org/builders/buildbase-lion-
x86_64/builds/867/steps/svn/logs/stdio buildbot log], the user trying to
run the svn command is buildbot, so maybe that's the user who needs to
have the cert accepted:
{{{
sudo -u buildbot /usr/bin/svn info
https://svn.macports.org/repository/macports
}}}
--
Ticket URL: https://trac.macports.org/ticket/42727#comment:5
MacPorts http://www.macports.org/
Ports system for OS X
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #42727: Server certificate verification failed: issuer is not trusted (https://svn.macports.org
Okay, I executed it as user buildbot and it seems to have worked. Let me know if that has fixed the problem. Shree On Mar 10, 2014, at 12:09 AM, MacPorts nore...@macports.org wrote: #42727: Server certificate verification failed: issuer is not trusted (https://svn.macports.org -+- Reporter: ryandesign@…| Owner: wsiegrist@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting |Version: Resolution: | Keywords: Port: | -+- Comment (by ryandesign@…): Replying to [comment:7 jmr@…]: Building ports runs as root so it can add users. Ah, of course. Both builders are using `HOME=/buildbot/ports-slave` though, so I think svn will be looking there for its config. Accepting the cert permanently should create something under `$HOME/.subversion/auth/`. And one should copy that something to /buildbot/ports- slave/.subversion/auth then, yeah? -- Ticket URL: https://trac.macports.org/ticket/42727#comment:8 MacPorts http://www.macports.org/ Ports system for OS X ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #42727: Server certificate verification failed: issuer is not trusted (https://svn.macports.org
Clemens I tried that and it didn’t change the situation. Take a look at the permissions on the auth directory, the directories inside it seem to be more open. I wonder if that is what is causing it not to write to it? Shree eneight-slave:~ root# ls -ld /buildbot/ports-slave/.subversion/auth/ drwx-- 6 buildbot staff 204 Mar 7 2012 /buildbot/ports-slave/.subversion/auth/ teneight-slave:~ root# cd !$ cd /buildbot/ports-slave/.subversion/auth/ teneight-slave:auth root# ls svn.simple svn.ssl.server svn.ssl.client-passphrase svn.username teneight-slave:auth root# ls -l total 0 drwxr-xr-x 2 buildbot staff 68 Mar 7 2012 svn.simple drwxr-xr-x 2 buildbot staff 68 Mar 7 2012 svn.ssl.client-passphrase drwxr-xr-x 4 buildbot staff 136 Apr 4 2012 svn.ssl.server drwxr-xr-x 2 buildbot staff 68 Mar 7 2012 svn.username On Mar 10, 2014, at 5:03 PM, Clemens Lang c...@macports.org wrote: sudo -u buildbot env HOME=/buildbot/ports-slave svn info https://svn.macports.org/repository/macports/ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #42727: Server certificate verification failed: issuer is not trusted (https://svn.macports.org
Jeremy Looks like it worked on the four slaves except the svn info does the same on teneight-slave and tennine-slave for user “local”. It works fine as root and buildbot users. Let me know if this has made any difference. Shree On Mar 10, 2014, at 5:56 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: /buildbot/ports-slave/.subversion/auth/ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #42727: Server certificate verification failed: issuer is not trusted (https://svn.macports.org
Can you please confirm if snowleapord and mountainlion are okay? And only Lion and Mavericks need to fixed?Or am I completely wrong? Shree On Mar 10, 2014, at 9:37 PM, Joshua Root j...@macports.org wrote: Still failing, possibly because of the home dirs. See https://trac.macports.org/ticket/42727#comment:10 - Josh On 2014-3-11 15:17 , Shreeraj Karulkar wrote: Jeremy Looks like it worked on the four slaves except the svn info does the same on teneight-slave and tennine-slave for user “local”. It works fine as root and buildbot users. Let me know if this has made any difference. Shree On Mar 10, 2014, at 5:56 PM, Jeremy Lavergne jer...@lavergne.gotdns.org mailto:jer...@lavergne.gotdns.org wrote: /buildbot/ports-slave/.subversion/auth/ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #42727: Server certificate verification failed: issuer is not trusted (https://svn.macports.org
I just did teneight-slave base, can you check how it looks while I do the others. Shree On Mar 10, 2014, at 9:49 PM, Joshua Root j...@macports.org wrote: Both builders need fixing for Lion and Mavericks, only base needs fixing for Mountain Lion. Snow Leopard has always been OK because its svn knows about the system root certs. You can see the latest status at https://build.macports.org/waterfall. - Josh On 2014-3-11 15:44 , Shreeraj Karulkar wrote: Can you please confirm if snowleapord and mountainlion are okay? And only Lion and Mavericks need to fixed?Or am I completely wrong? Shree On Mar 10, 2014, at 9:37 PM, Joshua Root j...@macports.org wrote: Still failing, possibly because of the home dirs. See https://trac.macports.org/ticket/42727#comment:10 - Josh On 2014-3-11 15:17 , Shreeraj Karulkar wrote: Jeremy Looks like it worked on the four slaves except the svn info does the same on teneight-slave and tennine-slave for user “local”. It works fine as root and buildbot users. Let me know if this has made any difference. Shree On Mar 10, 2014, at 5:56 PM, Jeremy Lavergne jer...@lavergne.gotdns.org mailto:jer...@lavergne.gotdns.org wrote: /buildbot/ports-slave/.subversion/auth/ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #42727: Server certificate verification failed: issuer is not trusted (https://svn.macports.org
Josh I am done with all three. Can you kick off your builds and let me know how it goes. Shree On Mar 10, 2014, at 9:49 PM, Joshua Root j...@macports.org wrote: Both builders need fixing for Lion and Mavericks, only base needs fixing for Mountain Lion. Snow Leopard has always been OK because its svn knows about the system root certs. You can see the latest status at https://build.macports.org/waterfall. - Josh On 2014-3-11 15:44 , Shreeraj Karulkar wrote: Can you please confirm if snowleapord and mountainlion are okay? And only Lion and Mavericks need to fixed?Or am I completely wrong? Shree On Mar 10, 2014, at 9:37 PM, Joshua Root j...@macports.org wrote: Still failing, possibly because of the home dirs. See https://trac.macports.org/ticket/42727#comment:10 - Josh On 2014-3-11 15:17 , Shreeraj Karulkar wrote: Jeremy Looks like it worked on the four slaves except the svn info does the same on teneight-slave and tennine-slave for user “local”. It works fine as root and buildbot users. Let me know if this has made any difference. Shree On Mar 10, 2014, at 5:56 PM, Jeremy Lavergne jer...@lavergne.gotdns.org mailto:jer...@lavergne.gotdns.org wrote: /buildbot/ports-slave/.subversion/auth/ ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
