Troubleshooting - Revision history

Lakshmi at 09:04, 4 August 2023

2023-08-04T09:04:23Z

Lakshmi at 09:02, 4 August 2023

2023-08-04T09:02:32Z

Lakshmi: Blanked the page

2023-08-04T07:24:02Z

Blanked the page

Sachin at 11:00, 10 March 2021

2021-03-10T11:00:01Z

Sachin at 10:17, 10 March 2021

2021-03-10T10:17:42Z

Sachin: Created page with "'''Issue:Tranzman client process is not running on Linux platforms. What should I do ? * Some *nix platforms have restrictions on the /tmp folder that prevent Tranzman from be..."

2021-03-10T10:11:48Z

Created page with "'''Issue:Tranzman client process is not running on Linux platforms. What should I do ? * Some *nix platforms have restrictions on the /tmp folder that prevent Tranzman from be..."

New page

'''Issue:Tranzman client process is not running on Linux platforms. What should I do ?
* Some *nix platforms have restrictions on the /tmp folder that prevent Tranzman from being able to run.
* When Tranzman processes run, they create temporary files in /tmp, but if they are not able to do so you get errors like.

Can't load '/tmp/p2xtmp-2834371/auto/Socket/Socket.so' for module Socket: /tmp/p2xtmp-2834371/auto/Socket/Socket.so: failed to map segment from shared object at PERL2EXE_STORAGE/DynaLoader.pm line 190.
at PERL2EXE_STORAGE/Net/FTP.pm line 17
Compilation failed in require at PERL2EXE_STORAGE/Net/FTP.pm line 17.
BEGIN failed--compilation aborted at PERL2EXE_STORAGE/Net/FTP.pm line 17.
Compilation failed in require at /home/d5122270-871/tzm_recorder/tzm_recorder line 34.
BEGIN failed--compilation aborted at /home/d5122270-871/tzm_recorder/tzm_recorder line 34

To overcome this issue we can set the TEMP environment variable as follows.

make a tmp folder in the folder where the tranzman tools / processes have been extracted.

mkdir /home/adminuser/tzm_recorder/tmp
export TEMP=/home/adminuser/tzm_recorder/tmp
chmod 775 /home/adminuser/tzm_recorder/tmp

then re-run the relevant tranzman tools / processes.

← Older revision		Revision as of 09:04, 4 August 2023
Line 63:		Line 63:
	* If there are missing mappings, the <b>CreateMedia</b>, <b>CreateConfig</b> and <b>CreateWorkloads</b> will fail.		* If there are missing mappings, the <b>CreateMedia</b>, <b>CreateConfig</b> and <b>CreateWorkloads</b> will fail.
	* <b>ManipulateImages</b> will also move associated images to the Intervention state, as they can not be migrated until the renames are fixed.		* <b>ManipulateImages</b> will also move associated images to the Intervention state, as they can not be migrated until the renames are fixed.
		+
		+
		+
		+	{\| class="wikitable" style="margin:auto;width:100%;color:blue;text-align:center;borderstyle=ridge;"
		+	\|-
		+	\| [[Image:prev_icon.jpg\|30px\|link=Finalize]]
		+	\|\| [[Image:next_icon.jpg\|30px\|link=Cleanup]]
		+	\|}

← Older revision	Revision as of 09:02, 4 August 2023
Line 1:	Line 1:
	+	===Introduction===
	+	<b>Tranzman</b> UI has the flexibility and functionality to help verify and troubleshoot issues without requiring additional login to server.

	+	Agent communication/connectivity issues can be troubleshooted from <b>Dashboard</b>
	+	Any migration issues can be veiwed from <b>Activities</b> or <b>Alerts</b>
	+
	+
	+	===Downloading Support Package===
	+	Support package can be generated by clicking on the <i>downloads</i> icon of corresponding Task.
	+	<!image>
	+	The Support Package is generated in zip format.
	+	The package includes -
	+	* <i>Inbound</i> folder with data that was sent back from the agent
	+	* <i>Outbound</i> folder with the api.out and other supporting files
	+	* <jobid>.log, a dump of the logs for the given action jobID
	+	* <i>Revisions.txt</i> a list of the current patch files applied.
	+	The package contains the api list of commands that were run for a given action, along with all the supporting files being sent to the agent, and the files that the agent has returned.
	+	The package should have sufficient data/logs to troubleshoot the issue.
	+
	+
	+	===Agent connection issues===
	+	By default, Agent uses <i>SSL</i> connections -
	+	* The Agent will default using cURL for all communication to the TZM appliance over port #55560.
	+	* cURL may behave differently for different versions, some send EMPTY files even if no file exists
	+	* If cURL communication cannot be established, then the communication can be switched to legacy FTP mode.
	+
	+	FTP is used as a fail-back option
	+	* Requires a range of ports to be open 55000 to 55555 on the TZM appliance
	+	* Port 55555 is the primary port used to establish communication
	+	* Unlike FTP, the data over Tranzman FTP is obfuscated.
	+
	+	On the Agent side -
	+	* Look for any errors in <b>tzmclnt.log</b>(<i><installpath>/tzmclnt</i>)
	+	* Ensure the required ports are open
	+	* Verify the version of cURL is working correctly
	+	* For more debugging logs - use tzmclnt with <i>-output</i> option.
	+
	+
	+	===Troubleshooting Config Object migration===
	+	* Identify the failed api from <b>Activities</b> or <b>Alerts</b>
	+	* If there were issues with components being migrated, manual intervention may be required to create those items on the destination.
	+	* After manual creation, the items can be marked as imported to tell <b>Tranzman</b> not to retry migrating the same component.
	+	* If the object doesn’t need to be migrated it can be marked as deselected / ignored
	+
	+
	+	===Troubleshooting Image migration===
	+	* If there were issues with images being migrated, manual intervention may be required to reset and retry or to deselect them.
	+	* Verify the reason for the Iamge failure using <b>Views</b>-><b>Images</b> and clicking on the image.
	+	* <i>Missing files</i> during <b>Export Images</b> require investigation on the origin, and likely a cat_export issue of image headers.
	+	It can also mean the symbolic links or ALTPATH files point to invalid locations on the origin, or that other files are missing from the Origin.
	+	* <i>Missing files</i> during <b>Import Images</b> can happen if a clean-up run at the same time as Tranzman doing the import. These images should be reset to transfer them again and further investigation is required if failure repeats.
	+	* Images that are in an Intervention state, are missing a rename rule for the DISK MEDIA ID, HOST, or SLP, and there will be entries in the rename rules that needs to be changed from MISSING_XXXX_MAPPING to a valid configuration. Reset the images after fixing the rename rules, to allow it to retry.
	+	* If there is an issue with missing files, and they exist on the Origin, they can be manually copied over and then the image can be marked as imported. Extra care is required if image header is manually modified and use cat_import to import them. Perform this only under support supervision!
	+
	+
	+	===Troubleshooting missing mappings===
	+	(MISSING_HOST_MAPPING, MISSING_DISK_MAPPING, MISSING_SLP_MAPPING)
	+	* When ManipulateImages runs and identifies that an image header is referring to:
	+	** an SLP (with SLP status or 1 or 2) and where that SLP has not been selected or has not been renamed.
	+	** a Disk mediaID or BasicDisk path is missing rename rule.
	+	** a Media Server that is not selected or renamed.
	+	* When Apply Rules run, it looks to ensure that all Media Servers referred in images have been selected or have a valid rename rule. Missing rename rule creates a MISSING_HOST_MAPPING entry.
	+	* If there are missing mappings, the <b>CreateMedia</b>, <b>CreateConfig</b> and <b>CreateWorkloads</b> will fail.
	+	* <b>ManipulateImages</b> will also move associated images to the Intervention state, as they can not be migrated until the renames are fixed.

← Older revision		Revision as of 07:24, 4 August 2023
Line 1:		Line 1:

−	~~'''Issue : Tranzman client process is not running on Linux platforms. What should I do ?~~
−	* Some *nix platforms have restrictions on the /tmp folder that prevent Tranzman from being able to run.
−	* When Tranzman processes run, they create temporary files in /tmp, but if they are not able to do so you get errors like.
−
−	Can't load '/tmp/p2xtmp-2834371/auto/Socket/Socket.so' for module Socket: /tmp/p2xtmp-2834371/auto/Socket/Socket.so: failed to map segment from shared object at PERL2EXE_STORAGE/DynaLoader.pm line 190.
−	~~at PERL2EXE_STORAGE/Net/FTP.pm line 17~~
−	~~Compilation failed in require at PERL2EXE_STORAGE/Net/FTP.pm line 17.~~
−	~~BEGIN failed--compilation aborted at PERL2EXE_STORAGE/Net/FTP.pm line 17.~~
−	~~Compilation failed in require at /home/d5122270-871/tzm_recorder/tzm_recorder line 34.~~
−	~~BEGIN failed--compilation aborted at /home/d5122270-871/tzm_recorder/tzm_recorder line 34~~
−
−	~~To overcome this issue we can set the TEMP environment variable as follows.~~
−
−	~~make a tmp folder in the folder where the tranzman tools / processes have been extracted.~~
−
−	~~mkdir /home/adminuser/tzm_recorder/tmp~~
−	~~export TEMP=/home/adminuser/tzm_recorder/tmp~~
−	~~chmod 775 /home/adminuser/tzm_recorder/tmp~~
−
−	~~then re-run the relevant tranzman tools / processes.~~

@@ Line 1: / Line 1: @@
-'''Issue:Tranzman client process is not running on Linux platforms. What should I do ?
+'''Issue : Tranzman client process is not running on Linux platforms. What should I do ?
 * Some *nix platforms have restrictions on the /tmp folder that prevent Tranzman from being able to run.
 * When Tranzman processes run, they create temporary files in /tmp, but if they are not able to do so you get errors like.

← Older revision		Revision as of 10:17, 10 March 2021
Line 1:		Line 1:
		+
	'''Issue:Tranzman client process is not running on Linux platforms. What should I do ?		'''Issue:Tranzman client process is not running on Linux platforms. What should I do ?
	* Some *nix platforms have restrictions on the /tmp folder that prevent Tranzman from being able to run.		* Some *nix platforms have restrictions on the /tmp folder that prevent Tranzman from being able to run.