Showing posts with label troubleshooting. Show all posts
Showing posts with label troubleshooting. Show all posts
Friday, September 8, 2017
Troubleshooting Firebird Database
Troubleshooting Firebird Database
Note: I will be using the employee database(/opt/firebird/examples/empbuild/employee.fdb) which is available by-default with the Firebird 2.5.7 in this post.
How to connect to a Firebird Database and test (using command-line)
1. Go to /opt/firebird/bin directory.
2. Run ./isql (Command-line tool for Firebird)
udara@Razorx1:/opt/firebird/bin$ ./isql3. Run connect "/opt/firebird/examples/empbuild/employee.fdb"
Use CONNECT or CREATE DATABASE to specify a database
SQL>
SQL> connect "/opt/firebird/examples/empbuild/employee.fdb"4. Provide the user/password to connect, note the semicolon (;) at the end.
CON>
CON> user SYSDBA password admin;
Database: "/opt/firebird/examples/empbuild/employee.fdb", User: SYSDBA
SQL>
5. Run the intended query,
SQL> select * from employee;
EMP_NO FIRST_NAME LAST_NAME PHONE_EXT HIRE_DATE DEPT_NO JOB_CODE JOB_GRADE JOB_COUNTRY SALARY FULL_NAME
======= =============== ==================== ========= ========================= ======= ======== ========= =============== ===================== =====================================
2 Robert Nelson 250 1988-12-28 00:00:00.0000 600 VP 2 USA 105900.00 Nelson, Robert
4 Bruce Young 233 1988-12-28 00:00:00.0000 621 Eng 2 USA 97500.00 Young, Bruce
5 Kim Lambert 22 1989-02-06 00:00:00.0000 130 Eng 2 USA 102750.00 Lambert, Kim
8 Leslie Johnson 410 1989-04-05 00:00:00.0000 180 Mktg 3 USA 64635.00 Johnson, Leslie
9 Phil Forest 229 1989-04-17 00:00:00.0000 622 Mngr 3 USA 75060.00 Forest, Phil
11 K. J. Weston 34 1990-01-17 00:00:00.0000 130 SRep 4 USA 86292.94 Weston, K. J.
12 Terri Lee 256 1990-05-01 00:00:00.0000 000 Admin 4 USA 53793.00 Lee, Terri
How to enable trace configuration
1. Open /opt/firebird/fbtrace.conf in your favorite text editor and update relevant configuration.How to trace the database
1. Go to /opt/firebird/bin directory.2. Run ./fbtracemgr with proper parameter set.
udara@Razorx1:/opt/firebird/bin$ ./fbtracemgr -SE service_mgr -START -NAME fire -CONFIG ../fbtrace.conf -USER SYSDBA -PASS admin
Sample trace output for the select * from employee;query.
2017-02-22T11:58:23.2200 (1980:0x7f85df7ae678) TRACE_INIT
SESSION_4 fire
2017-02-22T11:58:23.2210 (1980:0x7f85df7ae678) PREPARE_STATEMENT
/opt/firebird/examples/empbuild/employee.fdb (ATT_63, SYSDBA:NONE, NONE, TCPv4:127.0.0.1)
/opt/firebird/bin/isql:7445
(TRA_264, READ_COMMITTED | NO_REC_VERSION | WAIT | READ_WRITE)
Statement 128:
-------------------------------------------------------------------------------
select * from employee
0 ms
2017-02-22T11:58:23.2210 (1980:0x7f85df7ae678) FREE_STATEMENT
/opt/firebird/examples/empbuild/employee.fdb (ATT_63, SYSDBA:NONE, NONE, TCPv4:127.0.0.1)
/opt/firebird/bin/isql:7445
Statement 127:
-------------------------------------------------------------------------------
select * from employee
2017-02-22T11:58:23.2220 (1980:0x7f85df7ae678) EXECUTE_STATEMENT_START
/opt/firebird/examples/empbuild/employee.fdb (ATT_63, SYSDBA:NONE, NONE, TCPv4:127.0.0.1)
/opt/firebird/bin/isql:7445
(TRA_263, CONCURRENCY | WAIT | READ_WRITE)
Statement 128:
-------------------------------------------------------------------------------
select * from employee
2017-02-22T11:58:23.2260 (1980:0x7f85df7ae678) CLOSE_CURSOR
/opt/firebird/examples/empbuild/employee.fdb (ATT_63, SYSDBA:NONE, NONE, TCPv4:127.0.0.1)
/opt/firebird/bin/isql:7445
Statement 128:
-------------------------------------------------------------------------------
select * from employee
Firebird trace utility
Firebird Trace utility.
Usage: fbtracemgr <action> [<parameters>]
Actions:
-STA[RT] Start trace session
-STO[P] Stop trace session
-SU[SPEND] Suspend trace session
-R[ESUME] Resume trace session
-L[IST] List existing trace sessions
Action parameters:
-N[AME] <string> Session name
-I[D] <number> Session ID
-C[ONFIG] <string> Trace configuration file name
Connection parameters:
-SE[RVICE] <string> Service name
-U[SER] <string> User name
-P[ASSWORD] <string> Password
-FE[TCH] <string> Fetch password from file
-T[RUSTED] <string> Force trusted authentication
Examples:
fbtracemgr -SE remote_host:service_mgr -USER SYSDBA -PASS masterkey -LIST
fbtracemgr -SE service_mgr -START -NAME my_trace -CONFIG my_cfg.txt
fbtracemgr -SE service_mgr -SUSPEND -ID 2
fbtracemgr -SE service_mgr -RESUME -ID 2
fbtracemgr -SE service_mgr -STOP -ID 4
download file now
Friday, September 1, 2017
Troubleshooting Kali Linux Installation
Troubleshooting Kali Linux Installation
There could be various reason for installation failure. Few of the basic reasons are corrupted downloadable file, damage media during writing an iso file, in-sufficient disk space, missing hash file etc. Click here to open the link and read this article on Troubleshooting Kali Linux Installation.
download file now
Saturday, August 26, 2017
Troubleshooting Methodology
Troubleshooting Methodology
In my many years of troubleshooting IT problems, and working with many many colleagues, I
have seen the good and the bad of troubleshooting technique. This post is not going to go into
any particular technology, it aims to set out an ideology for troubleshooting a failed system
where there is no known fix.
Pre-requisites- Technical aptitude.- An understanding of the concepts behind how the failed system works.- Sufficient access to the logs, management consoles, and diagnostic tools for the system in question.- Curiosity. Be curious and have a good look around (time permitting) through the logs, management consoles, and diagnostics tools; something glaringly obvious might become apparent!- Time. Time might be very scarce if the failed system is of critical importance, still, it is important to take the time to absorb the information that is available in-front of you, in order to come to a diagnosis.- Have the grace to admit when you are beaten and escalate before too much time is lost if the system is mission critical!
Note: To be a good IT Technical Troubleshooter, you do not need to be a guru, you do not need to be super intelligent, you do not even need to have seen or have experience of the failed system before, you just need the pre-requisite technical aptitude, and be able to apply logic to the problem at hand.
Rules
- Do not make the problem worse!- Before making any major change in order to fix the problem, be certain to first check with available sources of potentially useful knowledge (e.g. colleagues, Google and the internet, troubleshooting manuals, support channels, �.)
Troubleshooting the Failed System
Approach the problem in-hand with a clear mind and in the following logical way:
- Every system needs a certain chain of events to be satisfied in order to work; follow through the systems operational process checking off each link in the chain to find the broken link (of course one can to jump straight to the broken link when it becomes obvious what it is.)E.g. For this to work, first this, this, this, this, �, and this must work!
*Many thanks to David Castillo Dominici of FreeDigitalPhotos.net for the image.
- It often happens that all the links in the chain check out okay, upon which there is still the option to allow the system to go through its operational process from the start of the chain (reboot.)
Tips and Things To Remember
- Do not jump to any assumptions or assertions!- Do not make a rash judgement.- �There is nothing in our lives that is permanent.� Just because something shouldnt have changed, doesnt mean it wont have changed.- Do not expect to know everything; consult with sources of knowledge (colleagues, the web, manuals, �) and do not be afraid to ask for help. "To admit you dont know everything is the first step on the road to wisdon."- Take the words of others with a pinch of salt � be sure to check things yourself.
download file now
Thursday, August 10, 2017
Troubleshooting Wireless Driver
Troubleshooting Wireless Driver
Troubleshooting wireless driver in Linux is a tedious task, if you do not know what to look for. Here is the link that will guide you to do basic troubleshooting to resolve wireless issue. Click here to goto the article page.
download file now
Monday, August 7, 2017
Troubleshooting ORA 16191 ORA 01017
Troubleshooting ORA 16191 ORA 01017
In 11gR1, 11gR2, ambience up log carriage for DataGuard, Streams, CDC, etc., you are acceptable to run into this annoyance. No amount how anxiously you accomplish the SYS passwords in the passwordfile the aforementioned byte-for-byte on both the antecedent and destination hosts, the antecedent archiver will abort aggravating to log in to the destination DB with these letters accounting to the active log:
ORA-01017: invalid username/password; logon denied
ORA-16191: Primary log shipping client not logged on standby
The band-aid is to actualize the passwordfiles with orapwd application the altercation ignorecase=y:
% orapwd file=orapwORCL password=sys_password ignorecase=y entries=5 force=y
This affair has been accurate by several bloggers and appointment participants, but there is still no agenda in Metalink as of today. Im not abiding what allotment of the codepath contains this bug or if conceivably this is one of those that would be addressed with the "not a bug" acknowledgment from dev. You will apparently accept begin this commodity afterwards afterward the instructions in the absurdity documentation:
download file now
Saturday, August 5, 2017
Troubleshooting Lync Edge 101
Troubleshooting Lync Edge 101
We installed a "simple" Lync Edge system with collocated Front-End and Mediation server and Enterprise Voice connected to the PSTN via a Nortel CS1000 PBX.
After configuring (among other things)
- Internal DNS
- External DNS
- Routing on the EdgeServer
- Internal Certificate
- External Certificate
- Public IP addresses
- Primary DNS suffix on the EdgeServer
- Open ports on the Internal Firewall
- Open ports on the External Firewall
- The mediation server to find the PBX
- The PBX with a SIP Trunk
- The topology, exported it and imported it on the EdgeServer
- Users with external access, enterprise voice and a valid line URI
- A Voice Policy, PSTN Usage and Route
- Automatic login internally and externally
and checking the configuration a few times, we could call�
External Lync <---> Internal Lync
Internal Lync <---> Mobile Phone
But not�
External Lync ---> Mobile Phone
Mobile Phone <--- External Lync
The signalling from the External Lync client to the Mobile phone went through, the phone would ring and we could answer the call. On the external Lync client the status shifted from "Calling" to "Connecting call", where it sat for a few seconds and finally displayed "Call failed due to network issues". This indicated that the signalling path were working fine and the problem was happening as the system tried to setup the media stream.
We then used the Lync Server 2010 Logging tool to find this error message:
"Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote"
Which led us to this post on the Lync forums: Incoming PSTN call to external user fails to connect
After investigating the logs some more we saw that the mediation server tried to establish a media path straight to the external client!? Did it not know we had an edge? - No, it actually did not!
After looking in the Lync Control Panel / Topology / Standard Edition / Mediation Server, we noticed that the EdgeServer setting were "Not Set"
With Power Shell we could check this with the following command:
Get-CsService -MediationServer
Identity : MediationServer:standard.kressmark.com
Registrar : Registrar:standard.kressmark.com
EdgeServer :
SipServerPort : 5070
SipClientTcpPort : 5060
SipClientTlsPort : 5067
AudioPortStart : 49152
AudioPortCount : 8348
DependentServiceList : {PstnGateway:10.10.10.40}
ServiceId : 1-MediationServer-4
SiteId : Site:Stockholm
PoolFqdn : standard.kressmark.com
Version : 5
Role : MediationServer
Also, in the Lync Control Panel / Topology / edge.kressmark.com / Edge Server / Dependents, we could only find �Registrar:�� and �ConferencingServer:�� and no "MediationServer:....
So our Mediation Server did not know we had an Edge, and the Edge server did not know about the Mediation server. My guess is that internal calls to PSTN worked simply because the Mediation server were collocated with the Standard server.
However, we used the following command to make things right:
Set-CsMediationServer -Identity "MediationServer:standard.kressmark.com" -EdgeServer edge.kressmark.com
And after restarting the Lync control panel it displayed correct data, and calls from the external Lync client via the collocated mediation server to PSTN worked (and the other way around as well!)
Puh!
download file now
Subscribe to:
Posts (Atom)