Sergey

I think you meant to say if you run service on port *=< 1024* you need root
privilages


On Wed, May 9, 2012 at 3:41 PM, Sergey Kobzar <sergey.kob...@itcraft.org>wrote:

> On Linux to run service on port >1024 you need root privileges. Non-root
> users can run services on ports >1024.
>
> http://www.staldal.nu/tech/**2007/10/31/why-can-only-root-**
> listen-to-ports-below-1024/<http://www.staldal.nu/tech/2007/10/31/why-can-only-root-listen-to-ports-below-1024/>for
>  example...
>
> On 05/09/12 02:25, George Kirkham wrote:
>
>> Mahmut,
>>
>> Thanks for your comments, the configuration that I am using is below,
>> are these settings the same or similar to how you run OpenMeetings or
>> port 80 ? If you don’t mind sharing, what is your server’s OS?, and what
>> would be your configuration settings that gets OpenMeetings to run on
>> port 80 instead of port 5080 ? Maybe there are other areas that I need
>> to modify other that the two that I am currently changing.
>>
>> /etc/init.d/red5
>>
>> start-stop-daemon --start -c nobody --pidfile $PIDFILE --chdir
>> $RED5_HOME --background --make-pidfile --exec $DAEMON >/dev/null
>> 2>/dev/null &
>>
>> /usr/lib/red5/conf/red5.**properties
>>
>> # HTTP
>>
>> http.host=0.0.0.0
>>
>> http.port=80
>>
>> https.port=8443
>>
>> http.URIEncoding=UTF-8
>>
>> /usr/lib/red5/webapps/**openmeetings/config.xml
>>
>> <red5httpport>80</**red5httpport>
>>
>> I run OpenMeetings using http://mydomain.com.au/ and it will redirect to
>> http://mydomain.com.au/**openmeetings<http://mydomain.com.au/openmeetings>but
>>  then there is no response from
>> the server.
>>
>> I am getting no error information from the log files.
>>
>> When I do netstat -anp | grep java
>>
>> tcp 0 0 127.0.0.1:8100 0.0.0.0:* LISTEN 4044/soffice.bin
>>
>> unix 2 [ ACC ] STREAM LISTENING 22175 4044/soffice.bin
>> /tmp/OSL_PIPE_0_**SingleOfficeIPC_**44e0c34da8623980ccf9f8299a62e4**fb
>>
>> tcp6 0 0 :::1935 :::* LISTEN 4051/java
>>
>> tcp6 0 0 :::9999 :::* LISTEN 4051/java
>>
>> However when I run as root user, then all works, see below for “netstat
>> -anp | grep java”
>>
>> /etc/init.d/red5
>>
>> start-stop-daemon --start -c root --pidfile $PIDFILE --chdir $RED5_HOME
>> --background --make-pidfile --exec $DAEMON >/dev/null 2>/dev/null &
>>
>> tcp 0 0 127.0.0.1:8100 0.0.0.0:* LISTEN 3880/soffice.bin
>>
>> unix 2 [ ACC ] STREAM LISTENING 21314 3880/soffice.bin
>> /tmp/OSL_PIPE_0_**SingleOfficeIPC_**44e0c34da8623980ccf9f8299a62e4**fb
>>
>> tcp6 0 0 :::1935 :::* LISTEN 3887/java
>>
>> tcp6 0 0 :::9999 :::* LISTEN 3887/java
>>
>> tcp6 0 0 :::8080 :::* LISTEN 3887/java
>>
>> tcp6 0 0 :::80 :::* LISTEN 3887/java
>>
>> tcp6 0 0 192.168.1.123:57440 192.168.1.123:3306 ESTABLISHED 3887/java
>>
>> tcp6 0 0 192.168.1.123:57443 192.168.1.123:3306 ESTABLISHED 3887/java
>>
>> unix 2 [ ] STREAM CONNECTED 21818 3887/java
>>
>> If I
>>
>> Thanks,
>>
>> George Kirkham
>>
>> IT Manager
>>
>> Cooperative Research Centre For Greenhouse Gas Technologies (CO2CRC)
>>
>> NFF House, 14 - 16 Brisbane Avenue, Barton, ACT, 2600, Australia
>>
>> T: (02) 6120 1600
>>
>> F: (02) 6273 7181
>>
>> E: gkirk...@co2crc.com.au <mailto:gkirk...@co2crc.com.au**>,
>>
>> W: www.co2crc.com.au <http://www.co2crc.com.au>
>>
>> *From:*Mahmut TEKER [mailto:teker.mah...@gmail.com**]
>> *Sent:* Wednesday, 9 May 2012 8:49 AM
>> *To:* 
>> openmeetings-user@incubator.**apache.org<openmeetings-user@incubator.apache.org>
>> *Subject:* Re: <red5httpport>80</**red5httpport>
>>
>> Hi George,
>>
>> I am using OM on port 80 and there is no problem. In fact I could not
>> understand your problem clearly. Can you post error messages or warnings
>> in the logs. That would make the issue clearer, I think.
>>
>> Moreover, there is an issue that, as I remember right, running
>> red5/openmeetings on a port below or equal 1200 requires to be root.
>>
>> Regards,
>>
>>
>> _Mahmut TEKER
>>
>> On 5/9/2012 12:23 AM, George Kirkham wrote:
>>
>> Stephen,
>>
>> The server is only for OpenMeetings, so no Apache running (or
>> installed), and nothing else on that port.
>>
>> I did find the difference, in my first server I was running openMeetings
>> as the root user, but with subsequent servers I had been using nobody.
>> Running OpenMeetings under nobody works well for port 5080, but not for
>> port 80, and I cannot understand why that might be.
>>
>> One thing I could try is to create a full account called “openmeetings”
>> which has a home directory and then try running OpenMeetings under this
>> account. Sometimes software requires an account with a home directory,
>> not just a dummy account.
>>
>> I believe the issue is related with OpenMeetings code somewhere, as the
>> Red5 server is running and accepting connections (root), just when you
>> try to run OpenMeetings itself, that fails.
>>
>> If I get success at any time, I will post back, but first I wanted to
>> learn if anyone was familiar with the issue, and it looks like everyone
>> else has their OpenMeetings servers either using port 5080 or are
>> successfully running under ‘nobody’.
>>
>> Thanks,
>>
>> George Kirkham
>>
>> IT Manager
>>
>> Cooperative Research Centre For Greenhouse Gas Technologies (CO2CRC)
>>
>> NFF House, 14 - 16 Brisbane Avenue, Barton, ACT, 2600, Australia
>>
>> T: (02) 6120 1600
>>
>> F: (02) 6273 7181
>>
>> E: gkirk...@co2crc.com.au <mailto:gkirk...@co2crc.com.au**>,
>>
>> W: www.co2crc.com.au <http://www.co2crc.com.au>
>>
>> *From:*Stephen Cottham 
>> [mailto:Stephen.Cottham@**robertbird.com.au<stephen.cott...@robertbird.com.au>
>> ]
>> *Sent:* Tuesday, 8 May 2012 10:34 PM
>> *To:* 
>> openmeetings-user@incubator.**apache.org<openmeetings-user@incubator.apache.org>
>> <mailto:openmeetings-user@**incubator.apache.org<openmeetings-user@incubator.apache.org>
>> >
>> *Subject:* RE: <red5httpport>80</**red5httpport>
>>
>> You aren’t using Apache on the new Debian server are you?
>>
>> If Apache is running on port 80 then they will conflict.
>>
>> To aid in finding the problem, If you go here
>>
>> /usr/lib/red5
>>
>> Then chmod 755 red5-debug.sh
>>
>> Then start it using the debug mode
>>
>> ./red5-debug.sh
>>
>> This will tell you more about why its failing to start.
>>
>> Cheers
>>
>> *Stephen Cottham**
>> *Group IT Manager (Associate)
>>
>> Robert Bird Group
>> Level 5, 333 Ann St
>> Brisbane, Queensland, 4000, Australia
>>
>> *Phone: +6173 319 2777 (AUS)*
>>
>> *Phone: +44207 592 8000 (UK)*
>>
>> *Fax: +6173 319 2799*
>>
>> *Mobile: +61400 756 963 (AUS)*
>>
>> *Mobile: +447900 918 616 (UK)*
>>
>> *Web: **www.robertbird.com* <http://www.robertbird.com/>
>>
>> <http://www.robertbird.com.au/**>
>>
>> This email and any attachments are confidential and may contain legally
>> privileged information or copyright material. Unless expressly stated,
>> confidentiality and/or legal privilege is not intended to be waived by
>> the sending of this email. The contents of this email, including any
>> attachments, are intended solely for the use of the individual or entity
>> to whom they are addressed. If you are not an intended recipient, please
>> contact us immediately by return email and then delete both messages.
>> You may not otherwise read, forward, copy, use or disclose this email or
>> any attachments. Any views expressed in this email are those of the
>> individual sender except where the sender expressly, and with authority,
>> states otherwise. It is your responsibility to check any attachments for
>> viruses or defects before opening or sending them on. None of the sender
>> or its related entities accepts any liability for any consequential
>> damage resulting from this email containing computer viruses.
>>
>>
>> Disclaimer added by *CodeTwo Exchange Rules*
>> www.codetwo.com <http://www.codetwo.com>
>>
>> *From:*George Kirkham [mailto:gkirk...@co2crc.com.au**]
>> *Sent:* Tuesday, 8 May 2012 1:24 PM
>> *To:* 
>> openmeetings-user@incubator.**apache.org<openmeetings-user@incubator.apache.org>
>> <mailto:openmeetings-user@**incubator.apache.org<openmeetings-user@incubator.apache.org>
>> >
>> *Subject:* <red5httpport>80</**red5httpport>
>>
>> Hi,
>>
>> Has anyone had success/issues with using port 80 instead of port 5080.
>>
>> I have a number of Debian OpenMeetings servers. The first that I built I
>> have configured using port 80 instead of port 5080, and all works well.
>>
>> Since that time I have built a few more Debian OpenMeetings servers and
>> I cannot get any of them to work with port 80. I really do not think the
>> issue is with OpenMeetings or its configuration, because I can copy the
>> entire “red5” folder from the new servers to the first (working) server
>> and it will work on port 80.
>>
>> I am hoping that someone may have had similar issues and knows how to
>> resolved it.
>>
>> Thanks,
>>
>> George Kirkham
>>
>> IT Manager
>>
>> Cooperative Research Centre For Greenhouse Gas Technologies (CO2CRC)
>>
>> NFF House, 14 - 16 Brisbane Avenue, Barton, ACT, 2600, Australia
>>
>> T: (02) 6120 1600
>>
>> F: (02) 6273 7181
>>
>> E: gkirk...@co2crc.com.au <mailto:gkirk...@co2crc.com.au**>,
>>
>> W: www.co2crc.com.au <http://www.co2crc.com.au>
>>
>> *From:*George Kirkham [mailto:gkirk...@co2crc.com.au**]
>> *Sent:* Monday, 7 May 2012 9:19 PM
>> *To:* 
>> openmeetings-user@incubator.**apache.org<openmeetings-user@incubator.apache.org>
>> <mailto:openmeetings-user@**incubator.apache.org<openmeetings-user@incubator.apache.org>
>> >
>> *Subject:* RE: FW: Editing OpenMeetings language files
>>
>> Thanks, Sebastian for your comments. It is good to know.
>>
>> George Kirkham
>>
>> *From:*seba.wag...@gmail.com <mailto:seba.wag...@gmail.com>
>> [mailto:seba.wag...@gmail.com]
>> *Sent:* Monday, 7 May 2012 5:23 PM
>> *To:* 
>> openmeetings-user@incubator.**apache.org<openmeetings-user@incubator.apache.org>
>> <mailto:openmeetings-user@**incubator.apache.org<openmeetings-user@incubator.apache.org>
>> >
>> *Subject:* Re: FW: Editing OpenMeetings language files
>>
>> Hi George,
>>
>> What is it that I should add to all the other language files?
>> => It makes it more easy to give a complete (but not fully translated)
>> file to translators. Lots of people tend to just download the
>> language-xml file and translate that. If those files are all incomplete
>> or certain labels are missing that this is just too confusing.
>>
>> The same English item, and then hope those with knowledge of the other
>> languages
>> modify for the languages that they are proficient in?
>> => Yes you can fill them up in English and hope that some translators
>> will look into that file. Of course it might take months or even years
>> until really all languages are filled up. You could also use
>> translate.google.com <http://translate.google.com> and look for a
>> translation.
>>
>> Maybe there are other practices that I would be good for me to follow,
>> if so, please let me know.
>> => If you edit the XML files please don't add linebreaks (some editors
>> do that automatically), if you want to include a "save" linebreak you
>> would actually enter something like this:
>>
>> &lt;br/&gt;
>>
>> (this is XML encoded HTML linebreak "<br/>")
>>
>>
>> Sebastian
>>
>> 2012/5/6 George Kirkham <gkirk...@co2crc.com.au
>> <mailto:gkirk...@co2crc.com.au**>>
>>
>> Hi,
>>
>> What is the correct process for adding a new item to the Language files
>> ?
>>
>> I have been informed that "If you add a new label we have a common
>> (undocumentated) rule: We add this label to all language files. You can
>> fill up other language files the english one. However all language files
>> should contain the same number of labels and not only a subset."
>>
>> What is it that I should add to all the other language files? The same
>> English item, and then hope those with knowledge of the other languages
>> modify for the languages that they are proficient in? Is there a way to
>> ask others to check and update any languages that they are proficient
>> in? Maybe there are other practices that I would be good for me to
>> follow, if so, please let me know.
>>
>> I noticed that the Japanese file has
>> <string id="262" name="salutation_miss">
>> <value>Ms.</value>
>> </string>
>>
>>
>> Thanks,
>>
>> George Kirkham
>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_**lock <https://twitter.com/#%21/dead_lock> <
>> https://twitter.com/#%21/**dead_lock <https://twitter.com/#%21/dead_lock>
>> >
>> http://www.openmeetings.de
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.**com <http://www.wagner-sebastian.com>
>> seba.wag...@gmail.com <mailto:seba.wag...@gmail.com>
>>
>>

Reply via email to