It workS! thank you guys so much to all of your effort and never stop
answering to my all of my silly questions. specially to Nick for having a
such very long patience.. hope that you can help me in establishing a
database in this stuff..:D cheers
On Fri, Mar 21, 2014 at 12:33 AM, Michael Anthony Balmes <
souskemic...@gmail.com> wrote:
> when i try kill that port.. my server will not be working..
>
>
> On Fri, Mar 21, 2014 at 12:08 AM, Branden Visser <mrvis...@gmail.com>wrote:
>
>> Hi Michael,
>>
>> As I said, you don't need to change that configuration. All you need
>> to do is shut down the existing Hilary process before you start a new
>> one.
>>
>> In your screen shot, you can see there is a node process with PID 5446
>> using the ports 2000 and 2001 (these are the ports that are already
>> configured in the config.servers object). If you try and start a new
>> node process without killing that one first, then you will get the
>> `EADDRINUSE` error.
>>
>> If you want to restart the Hilary server, first kill the existing
>> process with command:
>>
>> kill 5446
>>
>> Then when the ports are no longer occupied by Hilary, you can start
>> the server again.
>>
>>
>> On Thu, Mar 20, 2014 at 12:00 PM, Michael Anthony Balmes
>> <souskemic...@gmail.com> wrote:
>> > Hi sir,
>> >
>> > how should i configure this
>> >
>> > config.servers = {
>> > 'globalAdminAlias': 'admin',
>> > 'globalAdminHost': 'admin.oae.com',
>> > 'globalAdminPort': 2000,
>> > 'serverInternalAddress': null,
>> > 'tenantPort': 2001,
>> > 'useHttps': false,
>> > 'strictHttps': true
>> > };
>> >
>> >
>> > this is my status of sudo netstat -plnt. hope it will help you to verify
>> > what port will i stop first..i attached another print screen to this?i
>> > really confuse in my config.js.
>> >
>> >
>> >
>> > On Thu, Mar 20, 2014 at 6:08 PM, Branden Visser <mrvis...@gmail.com>
>> wrote:
>> >>
>> >> Please remember to use "Reply To All" so the message goes to the
>> oae-dev
>> >> list.
>> >>
>> >> On Thu, Mar 20, 2014 at 5:57 AM, Michael Anthony Balmes
>> >> <souskemic...@gmail.com> wrote:
>> >> > how should i sir to stop the Hilary?or even know the port they are
>> >> > using..I
>> >> > was very newbie here and all i know is to follow what i read.
>> >> >
>> >>
>> >> To stop the server you send a kill signal to the node process. You
>> >> find the process ID by looking for the process using the `ps` command.
>> >> The 2 ports that the server listens to are configurable in the
>> >> config.js file [1] but you don't need to change that.
>> >>
>> >> [1] https://github.com/oaeproject/Hilary/blob/master/config.js#L73
>> >>
>> >> >
>> >> > On Thu, Mar 20, 2014 at 5:53 PM, Branden Visser <mrvis...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> On Thu, Mar 20, 2014 at 5:10 AM, Michael Anthony Balmes
>> >> >> <souskemic...@gmail.com> wrote:
>> >> >> > so sir, what do you suggest sir?how should i start the server? i
>> use
>> >> >> > this to
>> >> >> > start the server using this script, node app.js |
>> >> >> > node_modules/.bin/bunyan
>> >> >> > &..if I'm not gonna use this what would be your suggestion..
>> >> >> > the procedure that i did before is to run the nginx then this
>> >> >> > script..
>> >> >> >
>> >> >>
>> >> >> The method you are using to start the server is fine. You just need
>> to
>> >> >> remember to stop the server before you start it again. You cannot
>> have
>> >> >> 2 instances of the server running at the same time.
>> >> >>
>> >> >> >
>> >> >> > On Thu, Mar 20, 2014 at 5:04 PM, Branden Visser <
>> mrvis...@gmail.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> No I mean just Hilary needs to be shut down before starting a new
>> >> >> >> instance
>> >> >> >> of Hilary.
>> >> >> >>
>> >> >> >> That error means that 2 things are trying to listen on the same
>> >> >> >> port.
>> >> >> >>
>> >> >> >>
>> >> >> >> On Mar 19, 2014, at 10:03 PM, Michael Anthony Balmes
>> >> >> >> <souskemic...@gmail.com> wrote:
>> >> >> >>
>> >> >> >> what do you mean sir?before I start the nginx and hilary, i start
>> >> >> >> the
>> >> >> >> cassandra, rabbit-mq,redis server, etherpad, elasticsearch. do i
>> >> >> >> need
>> >> >> >> shutdown them all and just the nginx and hilary?is that what you
>> >> >> >> mean
>> >> >> >> sir?
>> >> >> >>
>> >> >> >>
>> >> >> >> On Thu, Mar 20, 2014 at 9:31 AM, Branden Visser <
>> mrvis...@gmail.com>
>> >> >> >> wrote:
>> >> >> >>>
>> >> >> >>> Hi Michael, this means that there is an instance of the server
>> >> >> >>> already
>> >> >> >>> running. You seem to be running the node process in the
>> background,
>> >> >> >>> so
>> >> >> >>> you have to make sure you shut down all instances of OAE before
>> you
>> >> >> >>> try and start a new one.
>> >> >> >>>
>> >> >> >>> Thanks,
>> >> >> >>> Branden
>> >> >> >>>
>> >> >> >>> On Wed, Mar 19, 2014 at 9:08 PM, Michael Anthony Balmes
>> >> >> >>> <souskemic...@gmail.com> wrote:
>> >> >> >>> > Hi sir,
>> >> >> >>> > I have just see this error upon starting my server script
>> >> >> >>> > everything
>> >> >> >>> > seems to be fine except this error eaddrinuse issue. i attach
>> a
>> >> >> >>> > print
>> >> >> >>> > screen
>> >> >> >>> > for this..all of the component seems to be running. as i
>> check it
>> >> >> >>> > using
>> >> >> >>> > sudo
>> >> >> >>> > netstat -plnt just to check if the port is running. I dont
>> know
>> >> >> >>> > what
>> >> >> >>> > I'm
>> >> >> >>> > missing so far. before
>> http://admin.sakaioae.jupinno.com/api/me
>> >> >> >>> > is
>> >> >> >>> > working
>> >> >> >>> > and not the nginx but now it seems nginx is working and the
>> >> >> >>> > server
>> >> >> >>> > is
>> >> >> >>> > not.
>> >> >> >>> > when i check on it is said that the server is in the process
>> of
>> >> >> >>> > restarting.
>> >> >> >>> > every now and then i look at it but doesnt change. I really
>> >> >> >>> > appreciate
>> >> >> >>> > your
>> >> >> >>> > effort guys in helping to build up this project.
>> >> >> >>> >
>> >> >> >>> > _______________________________________________
>> >> >> >>> > oae-dev mailing list
>> >> >> >>> > oae-dev@collab.sakaiproject.org
>> >> >> >>> > http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>> >> >> >>> >
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >
>> >> >
>> >
>> >
>>
>
>
_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev
