Wizz expects a session handling from the initial fare request right to the finishing of the booking within one and the same IP address. Hence, Wizz has been set to static routing. However, that is only half the problem solved as they monitor the traffic per IP address as well and cut it off as they suspect spamming. Therefore, a static routing solves one problem but may lead to blocking of the IP address used.

Wizz is in the a Nagios Check Group 'Flight-G-Request-host'. These alarms are not displayed to Operating in general but to the system admins (i. e. Frank, Konny, Thorsten, Ingo etc).

Currently, as the Wizz Alarm is down we need to check if the string returned has a 'Timeout' message in it. If so we must inform Christian, #technik & technik@netzperten.de with Subject: WIZZ AIR Partners - Timeout Problem to change the static IP address and line for Wizz requests.

That should solve the problem in the short run.

520

This server contains archived prodlogfiles for expedia and LFX

In case of any errors do the following steps:

(On Monday mornings the upload will take more time, so sometimes the check is critical at 9:00. Pls reschedule the check 30 min later)

NagiosError "prodlogs archive files":

The upload of the LFX prodlogdir was not successfull at last run.

Check the files on prodlog-nas and the sql server. If you see a difference, contact technik

for Expedia on xpdmysql01:

/root/bin/prodlog_upload_by_hand.sh /home/backup/mysqlsicherung/101026/ xpdmysql-<year><month><day>

Replace "<year><month><day>" with the missing filedata (ls is your friend). For example:
/root/bin/prodlog_upload_by_hand.sh /home/backup/mysqlsicherung/101026/ xpdmysql-101026

This upload runs only during the week. On Weekends no prodlogfile will be produced.

Nagioserror "filesize"

delete the oldest prodlogfiles from "d:" on prodlog-nas

ID: 507

General:

Feature (in the Turbo Sabre Application) covering the LFAgent functionality to capture availability requests and transfer it to CWTWebfares in order to check for LowCost carrier availability.

Hence, CWT B2B agencies working with Turbo Sabre in paralell to their Sabre requests can check availability via CWTWebfares (similar to the LFAgent).

The Turbo Sabre requests are transferred via XML API, but the agencies being accessed are B2B (project LFC) agencies. Therefore, a dedicated XML Client (CWTXMLAPISabre) is set up in the CWT environment to receive the LFX requests and translate them into requests for project 'LFC' that can be processed for the existing B2B agencies.

In order to allow asynchronous processing (means Turbo Sabre need not to wait for any CWTWebfares replys) the SOAP Wrapper functionality was implemented by partners. The Turbo Sabre SOAP Wrapper creates an HTTP request which is transferred to the above mentioned client.
SOAP Wrapper uses a Windows Service (so not possible on LINUX).

The productive URL of the SOAP wrapper is working via cwtwf-prd06d.
There exists an alternativ URL (fall back) on cwtwf-prd07d.
Hence, if CWT detects any problems with the productive URL, they may change to the alternative one (without notifying partners). Which means for us, that BOTH have to be maintained and should be held available. Both is being monitored by Nagios.

As we are talking about Windows Services that are configured on the mentioned PCs, you will neither find a hint to 'Turbo Sabre SOAP Wrapper' in the watchdog, nor in the Autostart. They are started automatically in the moment the PC is started. In case of problems with the service a restart of the service (NOT necessarily the PC) is needed.

To (re)start the Windows Service (Windows Dienst)

for the SOAP Wrapper open 'Computer Management / Computerverwaltung' select 'Services and Applications' / 'Dienste+Anwendungen' and there 'Services / Dienste': LFProxyWinService should be 'Started / Gestarted'. If this one is not running, then start the Service via the link 'Restart the service / Den Dienst neu starten'.  (see attached screenshot)     

Nagios Error message "PATTERN NOT FOUND" - check G-requests

(search in TOFEHL for TOAGENT like 'IPSEN%'
and 'Text TEXT like '%ºF21LFA_TBOSABRE%' )

Maybe there is a general error with the airline?

In case the same search but for TOAGENT not like 'IPSEN%'  shows some successful requests this means that the live requests from the users work fine, but only the IPSEN requests for system maintenance have a problem. This would also point to an issue with the route/airline(s) being requested in the G-request stored.

                                                                                                 510

]]> http://faq.lowfare.de/index.php?action=artikel&cat=175&id=510&artlang=en Thu, 03 Nov 2011 09:12:43 GMT ADS.INI (7 views)

Falls PART.ONE oder eines seiner Module nicht funktioniert, so dann das daran liegen, dass die ADS.INI nicht vorhanden oder mit falschen Informationen bestückt ist.

Hier eine Beispiel-ADS.Ini:

If an applicationpool has high cpu load there is the possibility of restarting the pool.

1. You have to identify which exactly has the high cpu load for that open the taskmgr

Start > Execute > taskmgr > then go on Select Columns

Afterwards scroll down and put an mark the command line checkbox then press ok.

After that put a mark in the Show processes off all users checkbox.

After that open the commandline column as far as possible. At the end of the line you can see which applicationpool is standing behind the IIS Workerthread.

After that open the IIS Manager > Start > All Programs > Administrative Tools > IIS Manager. Then press on applicationpools to see all available pools.

To restart a single pool now that you have identified before just right click the pool and press recycling.

                                                                                                                         ID 429