Toolpack Troubleshooting:Web Portal: Difference between revisions
(creation) |
|||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
Cannot | == Cannot start the Web Portal == | ||
== Failed to connect == | === Verify that toolpack is running === | ||
tbtboolpack status | |||
=== Verify that web client is running === | |||
On linux: | |||
ps – ef | grep tbweb | |||
Output should be like this: | |||
tbweb 29609 1 0 Jul30 ? 00:00:36 /usr/sbin/lighttpd -D -f /lib/tb/toolpack/pkg/2.3.3/web/etc/lighttpd_12358.conf | |||
tbweb 29610 29609 0 Jul30 ? 02:29:16 /usr/bin/ruby /lib/tb/toolpack/pkg/2.3.3/web/public/dispatch.fcgi | |||
On windows: | |||
Start task manager | |||
Find tboamappctrl.ruby.exe | |||
=== Verify that tboamapp application is running === | |||
On linux: | |||
ps – ef | grep tboamapp | |||
Output should be like this: | |||
root 31647 31612 1 Aug24 ? 06:30:01 tboamapp | |||
On windows: | |||
Start task manager | |||
Find tboam_[version].tboamappctrl.exe | |||
=== Verify lighttpd instance === | |||
Stop Toolpack (tbtoolpack stop), then verify if there is a lighttpd process still running. | |||
*If there is one kill it, then restart Toolpack | |||
=== Start the Web Server manually === | |||
'''Note: For this Toolpack must be stopped'''. Start the web server manually and verify if there is an error. | |||
The command should look something like this(modify the line according to your package/[[System_Id|SystemId]]): | |||
lighttpd -D -f /lib/tb/toolpack/pkg/2.3.3/web/etc/lighttpd_12358.conf | |||
If there is no error the shell should NOT return and you should be able to connect to the Web Portal. If there is an error, it will displayed after the command. In that case please contact TelcoBridges support. | |||
== Cannot access the Web Portal == | |||
=== Verify lighttpd instance === | |||
For Unix host, verify that there is not 2 lighttpd instance using the same configuration file. | |||
*If they do, you should close or kill one. | |||
=== Failed to connect === | |||
Verify that the firewall(host and possibly network) enable http/https. | Verify that the firewall(host and possibly network) enable http/https. | ||
*Modify the firewall rules to accept incoming http and https request. | |||
== Web Portal queries fail == | |||
=== Check the logs === | |||
Verify the Web Portal logs located in: | |||
[InstallDirectory]/toolpack/pkg/[Version]/web/log | |||
Example | |||
/lib/tb/toolpack/pkg/2.3.3/web/log | |||
: | C:\TelcoBridges\toolpack\pkg\2.3.3\web\log | ||
Latest revision as of 09:57, 11 September 2009
Cannot start the Web Portal
Verify that toolpack is running
tbtboolpack status
Verify that web client is running
On linux:
ps – ef | grep tbweb
Output should be like this:
tbweb 29609 1 0 Jul30 ? 00:00:36 /usr/sbin/lighttpd -D -f /lib/tb/toolpack/pkg/2.3.3/web/etc/lighttpd_12358.conf tbweb 29610 29609 0 Jul30 ? 02:29:16 /usr/bin/ruby /lib/tb/toolpack/pkg/2.3.3/web/public/dispatch.fcgi
On windows:
Start task manager Find tboamappctrl.ruby.exe
Verify that tboamapp application is running
On linux:
ps – ef | grep tboamapp
Output should be like this:
root 31647 31612 1 Aug24 ? 06:30:01 tboamapp
On windows:
Start task manager Find tboam_[version].tboamappctrl.exe
Verify lighttpd instance
Stop Toolpack (tbtoolpack stop), then verify if there is a lighttpd process still running.
- If there is one kill it, then restart Toolpack
Start the Web Server manually
Note: For this Toolpack must be stopped. Start the web server manually and verify if there is an error.
The command should look something like this(modify the line according to your package/SystemId):
lighttpd -D -f /lib/tb/toolpack/pkg/2.3.3/web/etc/lighttpd_12358.conf
If there is no error the shell should NOT return and you should be able to connect to the Web Portal. If there is an error, it will displayed after the command. In that case please contact TelcoBridges support.
Cannot access the Web Portal
Verify lighttpd instance
For Unix host, verify that there is not 2 lighttpd instance using the same configuration file.
- If they do, you should close or kill one.
Failed to connect
Verify that the firewall(host and possibly network) enable http/https.
- Modify the firewall rules to accept incoming http and https request.
Web Portal queries fail
Check the logs
Verify the Web Portal logs located in:
[InstallDirectory]/toolpack/pkg/[Version]/web/log
Example
/lib/tb/toolpack/pkg/2.3.3/web/log C:\TelcoBridges\toolpack\pkg\2.3.3\web\log