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 IS&T 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
