Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Official Webserver module homepage broken
#16
fajo Wrote:Please run the following from command line:
Code:
httpd -f /raid/data/naswebsite/conf/httpd.conf -S
This gave me "Syntax OK" so I continued:
fajo Wrote:
Code:
>/raid/data/naswebsite/logs/error_log
httpd -f /raid/data/naswebsite/conf/httpd.conf -k start
That didn't give me any output on the console. Therefore I checked the module page (<!-- m --><a class="postlink" href="http://n4520/adm/getform.html?Module=webserver">http://n4520/adm/getform.html?Module=webserver</a><!-- m -->) and it said "Status running". Also I can now access NAS_IP:10080

Thanks for this, buddy. But why doesn't it work with Thecus WebUI??

Cheers
tobi
Reply
#17
Oh, and here is the content from error_log:

Quote:[Fri Dec 20 22:45:04 2013] [notice] SSL FIPS mode disabled
[Fri Dec 20 22:45:04 2013] [warn] RSA server certificate CommonName (CN) `Thecus Technology Corp.' does NOT match server name!?
[Fri Dec 20 22:45:05 2013] [notice] SSL FIPS mode disabled
[Fri Dec 20 22:45:05 2013] [warn] RSA server certificate CommonName (CN) `Thecus Technology Corp.' does NOT match server name!?
PHP Warning: PHP Startup: Unable to load dynamic library './curl.so' - ./curl.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './fileinfo.so' - ./fileinfo.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './gd.so' - ./gd.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './json.so' - ./json.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './mbstring.so' - ./mbstring.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './mcrypt.so' - ./mcrypt.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './mysql.so' - ./mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './mysqli.so' - ./mysqli.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './pdo.so' - ./pdo.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './pdo_mysql.so' - ./pdo_mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './pdo_sqlite.so' - ./pdo_sqlite.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './phar.so' - ./phar.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './posix.so' - ./posix.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './sqlite3.so' - ./sqlite3.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './sysvmsg.so' - ./sysvmsg.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './sysvsem.so' - ./sysvsem.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: PHP Startup: Unable to load dynamic library './sysvshm.so' - ./sysvshm.so: cannot open shared object file: No such file or directory in Unknown on line 0
[Fri Dec 20 22:45:05 2013] [notice] Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/1.0.0e-fips PHP/5.3.8 configured -- resuming normal operations
Reply
#18
Could you do a

Code:
ps -ef | grep httpd

please ... from the log, the server should be running and the startup script may just fail to detect it.

The PHP error messages are there because of the /raid/data/naswebsite/conf/php5/php.ini says:

Code:
extension_dir = "./"

which is complete nonsense. It should read

Code:
extension_dir = "/usr/lib/php/modules"

I wonder how this could pass QA ...

Cheers,
Falk
Further information und module downloads at FaJo.de

I decided to finally stop module development and maintenance. Existing modules are still available for download for now.
Reply
#19
fajo Wrote:
Code:
ps -ef | grep httpd

I MODIFIED this output as by explanation below:

Quote:[root@N4520 /]# ps -ef | grep httpd
10922 root 0:00 /usr/sbin/httpd -k start
11087 root 0:10 /usr/sbin/httpd -k start
11088 root 0:10 /usr/sbin/httpd -k start
11090 root 0:10 /usr/sbin/httpd -k start
11092 root 0:10 /usr/sbin/httpd -k start
11093 root 0:13 /usr/sbin/httpd -k start
11094 root 0:12 /usr/sbin/httpd -k start
11095 root 0:10 /usr/sbin/httpd -k start
11096 root 0:09 /usr/sbin/httpd -k start
14247 root 0:09 /usr/sbin/httpd -k start
14628 root 0:00 httpd -f /raid/data/naswebsite/conf/httpd.conf -k start
14634 musterma 0:00 httpd -f /raid/data/naswebsite/conf/httpd.conf -k start
14635 musterma 0:00 httpd -f /raid/data/naswebsite/conf/httpd.conf -k start
14636 musterma 0:00 httpd -f /raid/data/naswebsite/conf/httpd.conf -k start
14637 musterma 0:00 httpd -f /raid/data/naswebsite/conf/httpd.conf -k start
14638 musterma 0:00 httpd -f /raid/data/naswebsite/conf/httpd.conf -k start
14994 musterma 0:00 httpd -f /raid/data/naswebsite/conf/httpd.conf -k start
14995 musterma 0:00 httpd -f /raid/data/naswebsite/conf/httpd.conf -k start
15824 root 0:07 /usr/sbin/httpd -k start
16128 root 0:07 /usr/sbin/httpd -k start
16131 root 0:07 /usr/sbin/httpd -k start
18159 root 0:16 /usr/sbin/httpd -f /etc/httpd/conf/httpd_webdav.conf -k start
18394 root 0:00 /usr/sbin/httpd -f /etc/httpd/conf/httpd_webdav.conf -k start
18395 root 0:00 /usr/sbin/httpd -f /etc/httpd/conf/httpd_webdav.conf -k start
18396 root 0:00 /usr/sbin/httpd -f /etc/httpd/conf/httpd_webdav.conf -k start
18397 root 0:00 /usr/sbin/httpd -f /etc/httpd/conf/httpd_webdav.conf -k start
18398 root 0:00 /usr/sbin/httpd -f /etc/httpd/conf/httpd_webdav.conf -k start
30558 root 0:00 grep --color=auto httpd
[root@N4520 /]#

The user "musterma" in the quote above has been modified by myself and is not given in the console output. It is related to my local user as being set in ACL:
If user in ACL setting for "naswebsite" is: mustermann
the above log says: 'musterma".

But the problem is not related to the fact that my "user" has more than 8 characters right? It is just truncated in the output, isn't it?

/tobi
Reply
#20
Hi Tobi,

the output from "ps" clearly shows that the web server is running:

Code:
14638 musterma 0:00 httpd -f /raid/data/naswebsite/conf/httpd.conf -k start

The truncated name is normal (some decades ago some systems did not even accept user names longer than 8 characters. This just seems to be a left over from these times Wink

And ..... Thecus ran into exactly this trap too. They check if the server runs by issuing:

Code:
ps | grep "$HTTPD -k start" | grep -v "grep" | grep "${check_user}" | grep -v grep`

with

Code:
check_user = mustermann
HTTPD      = httpd -f /raid/data/naswebsite/conf/httpd.conf

This must fail if the length of the user name exceeds 8 characters. I do not even understand, why they check for the user name at all here as the path name of the config file clearly indicates that this is the webserver modules instance of httpd.

To fix the start script please run:

Code:
sed -i -e 's|get_procinfo .* grep -v grep|get_procinfo|' /opt/webserver/bin/start_http.sh
httpd -f /raid/data/naswebsite/conf/httpd.conf -k stop

Now try starting the webserver module from the WebUI.

Cheers,
Falk
Further information und module downloads at FaJo.de

I decided to finally stop module development and maintenance. Existing modules are still available for download for now.
Reply
#21
fajo Wrote:The truncated name is normal (some decades ago some systems did not even accept user names longer than 8 characters. This just seems to be a left over from these times Wink

Hey Falk,

I am more the hardware guy in my professional (and personal) life. However, I do know some basics about SW, and I do remember about the 8 characters limit back from "the good old times" Wink This is why I immediately thought this could be a point. Thanks for checking (and proving) that!

However, if a system relies on this limitation, this needs to be handled strict. In other words, I would be OK with the 8 characters when WebUI would have told me not to use any "user" with a name more than 8char....

fajo Wrote:To fix the start script please run:

Code:
sed -i -e 's|get_procinfo .* grep -v grep|get_procinfo|' /opt/webserver/bin/start_http.sh
httpd -f /raid/data/naswebsite/conf/httpd.conf -k stop

Now try starting the webserver module from the WebUI.

I ran these command and starting the webserver module went OK.

To verify the solution I again stopped the module (which went OK). Now when I restarted the module. First I get "port in use" error. But after some (ten) seconds, starting the server is possible again.

Thanks once more Falk.

When I see all these difficulties in Thecus official module(s) it is hard to believe that the problems I experienced lately should come from 3rd party App, as Thecus blames (I NEVER had any issue with Stephanes apache)... But it is always easier to blame others than investigate own mistakes/incompleteness/whatever.

So, at the end, shall I modify php.ini as you suggested?

fajo Wrote:The PHP error messages are there because of the /raid/data/naswebsite/conf/php5/php.ini says:

Code:
extension_dir = "./"

which is complete nonsense. It should read

Code:
extension_dir = "/usr/lib/php/modules"

Cheers,
tobi
Reply
#22
Hi Tobi,

yes, the change in php.ini should cause the warnings to disappear and the extensions to be loaded. Without this modification you will not be able to use mysql for example.

The delay between start and stop may be caused by apache itself as it tries to shut down cleanly allowing client sessions to terminate gracefully.

Cheers,
Falk
Further information und module downloads at FaJo.de

I decided to finally stop module development and maintenance. Existing modules are still available for download for now.
Reply
#23
Hi Tobi,

yes, the change in php.ini should cause the warnings to disappear and the extensions to be loaded. Without this modification you will not be able to use mysql for example.

The delay between start and stop may be caused by apache itself as it tries to shut down cleanly allowing client sessions to terminate gracefully.

Cheers,
Falk
Further information und module downloads at FaJo.de

I decided to finally stop module development and maintenance. Existing modules are still available for download for now.
Reply
#24
OK, changed php.ini

Now all i get in error_log when starting the module is:
Quote:[Sat Dec 21 00:11:02 2013] [notice] SSL FIPS mode disabled
[Sat Dec 21 00:11:02 2013] [warn] RSA server certificate CommonName (CN) `Thecus Technology Corp.' does NOT match server name!?
[Sat Dec 21 00:11:03 2013] [notice] SSL FIPS mode disabled
[Sat Dec 21 00:11:03 2013] [warn] RSA server certificate CommonName (CN) `Thecus Technology Corp.' does NOT match server name!?
[Sat Dec 21 00:11:03 2013] [notice] Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/1.0.0e-fips PHP/5.3.8 configured -- resuming normal operations
Reply
#25
OK, changed php.ini

Now all i get in error_log when starting the module is:
Quote:[Sat Dec 21 00:11:02 2013] [notice] SSL FIPS mode disabled
[Sat Dec 21 00:11:02 2013] [warn] RSA server certificate CommonName (CN) `Thecus Technology Corp.' does NOT match server name!?
[Sat Dec 21 00:11:03 2013] [notice] SSL FIPS mode disabled
[Sat Dec 21 00:11:03 2013] [warn] RSA server certificate CommonName (CN) `Thecus Technology Corp.' does NOT match server name!?
[Sat Dec 21 00:11:03 2013] [notice] Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/1.0.0e-fips PHP/5.3.8 configured -- resuming normal operations
Reply
#26
Hi Tobi,

yes, this is how it is expected to look like Wink

Cheers,
Falk
Further information und module downloads at FaJo.de

I decided to finally stop module development and maintenance. Existing modules are still available for download for now.
Reply
#27
Hi Tobi,

yes, this is how it is expected to look like Wink

Cheers,
Falk
Further information und module downloads at FaJo.de

I decided to finally stop module development and maintenance. Existing modules are still available for download for now.
Reply
#28
Hi,

Could Thecus please acknowledge the "8 character" bug in this module Fajo found? I think this is something that needs to be fixed in the next releases.

Cheers,
Tobi
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Official Transmission Module 2.92 Hixbot 1 1,976 10-06-2017, 08:15 AM
Last Post: Hixbot
  WebServer Module - Enabling CURL drukman 5 1,488 10-18-2013, 02:12 PM
Last Post: drukman
  WebServer Module 64bit Update drukman 7 2,205 10-14-2012, 04:24 PM
Last Post: Qoolbox
  WebServer Module 64bit Update 0 1,290 Less than 1 minute ago
Last Post:
  WebServer Module - Enabling CURL 0 918 Less than 1 minute ago
Last Post:
  Official Webserver module homepage broken 0 4,879 Less than 1 minute ago
Last Post:

Forum Jump:


Users browsing this thread: 1 Guest(s)