Re: Mac OS Forge Migration update

Any news on this, Shree? - Josh On 2014-3-18 06:43 , Shreeraj Karulkar wrote: > > 2) Ping issue: I have reopened the ticket which IS&T had resolved earlier. > 3/17 FireWall Rules for Mac OS Forge - ICMP . Will > let you know as soon as I find out.

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 ? IS&T are asking for this info to troubleshoot this fu

Re: Mac OS Forge Migration update

Yeah, still timing out from here: % ping distfiles.macports.org PING rsync.macports.org (17.251.224.217): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 ^C --- rsync.macports.org ping statistics --- 4 packets transmitted, 0 packets receiv

Re: Mac OS Forge Migration update

Prepending 'strace -f -t -T ' to the rsync command in deploy_archives.sh should do the trick, shouldn't it? The output will end up in the log for the deploy archives step. I just committed this change to svn, forgetting that you have to manually update since it's on the buildmaster. - Josh On 20

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 ru

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 wrote: > > The buildmaster is now receiving changesets, and selfupdate appears to > be working on the slaves too. Thanks! > > The failure to deplo

Re: Mac OS Forge Migration update

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.ma

Re: Mac OS Forge Migration update

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.macpo

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

Re: Mac OS Forge Migration update

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 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

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 AcceptLangu

Re: Mac OS Forge Migration update

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 reposi

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

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 wrote:

Re: [macosforge-leaders] Mac OS Forge Migration update

Hardcoded in /etc/hosts for some reason? On Mar 17, 2014, at 16:47, Shreeraj Karulkar 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 wrote: > >> Ryan >> >> I am a litt

Re: Mac OS Forge Migration update

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 ar

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 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

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:

Re: Mac OS Forge Migration update

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 l

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 da

Re: Mac OS Forge Migration update

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

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

Re: Mac OS Forge Migration update

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 wrote: > Thanks. The two pages are no

Re: Mac OS Forge Migration update

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 Karulk

Re: Mac OS Forge Migration update

One more issue: the buildmaster can't connect to packages.macports.org to upload the archives. See e.g. - Josh On 2014-3-14 17:24 , Joshua Root wrote: > Thanks Shree. Forgot to mention

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 wrote: > > Shree: > > A gentle reminder: > > Another outstanding issue for us is the M

Re: Mac OS Forge Migration update

Thanks Shree. Forgot to mention, even though builds are working, changesets apparently aren't being sent to buildbot from the svn hook. On 2014-3-14 16:57 , Shreeraj Karulkar wrote: > Josh > Thanks for confirming, I think we are going to need more additional rules to > be requested. Will keep you

Re: Mac OS Forge Migration update

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 d

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 wrote: > MacPorts buildslaves are connecting to the master now, but they still > can't connect to rsync.macports.org for selfu

Re: Mac OS Forge Migration update

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

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.