I am at a loss: SEP client gets 404 when connecting to the manager

I need a solution

cve.log debug output:

[2019-Jun-06 18:27:39.405925] [DEBUG] Loading data.
[2019-Jun-06 18:27:39.405925] [DEBUG] Loading data.
[2019-Jun-06 18:27:39.405925] [DEBUG] Attempting connection to server $MANAGER
[2019-Jun-06 18:27:39.405925] [INFO ] CallOneServer: Heartbeat pass <1> for $MANAGER
[2019-Jun-06 18:27:39.405925] [DEBUG] Heartbeat status: [complete: false] [successful: false]
[2019-Jun-06 18:27:39.405925] [DEBUG] Attempting to get Index2.xml file.
[2019-Jun-06 18:27:39.405925] [DEBUG] Current syed while downloading ssstem proxy is:
[2019-Jun-06 18:27:39.405925] [DEBUG] Setting CURL to use system proxy =
[2019-Jun-06 18:28:00.687198] [DEBUG] Interruptction=12&hostid=$HOSTID&chk=$CHK&ck=$CK&uchk=$UCHK&uck=$UCK&hid=$HID&groupid=$GROUPID&ClientProductVersion=14.2.3332.1000&mode=0&hbt=600&as=4770&cn=[hex]$CN&lun=[hex]$LUN&udn=[hex]$UDN
Downloaded 0 and uploaded 0 bytes.

I have tried pushing a new syslink from the SEPM, using the import function from the troubleshooting menu, and using syslinkdrop program, no joy.

In the past, reimporting the syslink was enough to restore the connection, but not this time.  I’m about ready to just do a nuke and repave on the clients that are having this problem, but would like to avoid the hassle of scheduling the downtime to do so.

Any ideas?

0

Related:

  • No Related Posts

Proxy unexpectedly got rebooted

I need a solution

Hi  Team,

Our both poxy got rebooted unexpectedly. One is last week and other is on this week.

I only can see software got rebooted. Please check below logs for more info and help me to find out the reason. 

ProxyA:-

Minicontext produced on: 2019-04-18 08:36:44+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.7.3.10.222765
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0xe
Software exception code: 0x0
Page fault linear address: 0x1d
Process group: “PG_TCPIP”
Process: “HTTP CW 2071A91EA40” in “libstack.exe.so” at .text+0x566abb

ProxyB:-

Minicontext produced on: 2019-04-10 22:38:47+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.7.3.10.222765
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0x0
Software exception code: 0x5a0000
Page fault linear address: 0x0
Process group: “PG_UNKNOWN”
Process: “Threshold_Monitor” in “” at .text+0x0

Thanks,

Mayur

0

1555596458

Related:

  • No Related Posts

Blocking Debug Programs

I need a solution

Hi,
I need to block the feature called SeDebugPrivilege for all users in my domain (even the administrators).
Is it possible to create a prevent policy on DCS for this?

example:
(sorry, my OS language is in portuguese, the event ID is 4672 and registered under security events)

feature to be blocked:
(Local Security Policy > User Rights Assignments > Debug Programs)
 

Thanks.

0

Related:

  • No Related Posts

Elastic Layering Logs

Debugging Elastic Layering problems is described in the documentation here (scroll down to Debug an Elastic Layer):

https://docs.citrix.com/en-us/citrix-app-layering/4/layer/assign-elastic-layers.html

Get the ELM logs first. Then:

1.Collect the data from these logs in the end-user VM after producing the problem:

  • Windows Application Event log: In the Windows Event Viewer under Windows Logs, export the Application event log as an EVTX file.
  • Unidesk Layering Service log (ulayersvc.log): C:ProgramDataUnideskLogsulayersvc.log
  • Unidesk LayerInfo log (layerinfo.log): %LOCALAPPDATA%UnideskLogslayerinfo.log (note, this is in the current user profile)

2.Collect the values of these Registry keys from the end-user VM:

  • HKEY_LOCAL_MACHINESOFTWAREUnideskULayerAssignmentFile
  • HKEY_LOCAL_MACHINESOFTWAREUnideskULayerRepositoryPath
  • HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsNTCurrentVersionWinlogonUserInit

3.Collect the contents of the JSON files, including at least the Assignment (ElasticLayerAssignments.json) and Layers (Layers.json) files from the Repository Path.

Enabling Debug Logging in Ulayer

By default, ulayersvc.log only logs events INFO or higher. You may determine that you want more detailed logging. To turn on DEBUG logging, you need to edit a configuration file. This can be done in a layer (preferably the Platform Layer) or by editing a published image after the fact. The setting must be present before Ulayer.exe starts, which normally means it must be present before the machine boots. So you cannot set it from a GPO, for instance.

Edit C:Program FilesUnideskLayering Servicesulayer.exe.config. Scroll down to find this block in the Log4Net Appender section:

<root>

<level value=”INFO“/>

<appender-ref ref=”LogFileAppender”/>

</root>

Change INFO to DEBUG and save.

Related:

  • No Related Posts

7023547: How to run GDB to debug a process in SMG

Step 2: Shutdown the module to be tested

This step is crucial to save the headache of dealing with modules trying to automatically reload.

If possible, shut down the program either with the modules UI page, or by sending a kill command to the module from a terminal window. If the kill command is used, it MUST NOT be used with the -9 switch, as this will not allow the module to stay down.

If shutting down the module is not possible, typically due to a crash/restart loop, disable the server setting for ‘Module auto-recovery’ under the Manage Servers UI page. With this setting disabled, the program will not come back up by itself. It is important to remember to re-enable this option when the back trace has been obtained.

Step 3: Ensure gdb is installed

To get the debug information, gdb is required, but it not installed by default.

Type ‘gdb –help’ at the terminal prompt to check that it is installed.

If the help page is not displayed, install gdb by typing ‘apt install gdb’.

Step 4: Run the module in debug mode

Using the startup command determined in step 1, we can now prepare to start the application. Using the examples from step 1, and assuming the module we are investigating is gwvsmtp, enter the following commands, noting the additional switch that has been added to the end of the line:

cd /opt/gwava/assets/bin/linux/x64

gdb --args /opt/gwava/assets/bin/linux/x64/gwvsmtp "/root=/opt/gwava/" /ServerId=1 /ModuleId=1 /ConsoleLog

After typing these commands you should be placed into the gdb program at a (gdb) prompt which is ready to run the application. Type ‘r’ to start the program.

Step 5: Watch and wait

Now that the program is running, it is simply a matter of waiting for the crash to occur. The /ConsoleLog switch that was included on the command line will be echoing to the terminal display. This is the same log information that is stored in the application logs. By emitting it during the debug session, we are able to capture the end of the log along with the debug information which saves on the effort of matching log files to the information we are after.

Leave the program running until it stops. This will be evident when the log stops scrolling and you are given a prompt to type at.

Step 6: Obtain the backtrace

Once the program fails, type ‘bt’ at the prompt. This will provide a set of lines that include the information that’s useful to engineering.

Scroll back up through the information to where the logging information ends. Copy the text from approximately one screenful of logging information down to the end of the backtrace information. Pay attention to what’s in the log information and if it seems that more may be useful, copy as much as seems necessary. It is better to capture more information than less if you are unsure of what you are reading. Using the time on the log can also be a useful way to determine what might be necessary. If there are four pages of log data within the same second, chances are that’s all going to be related.

The information should look something like this:

Step 7: Clean up

To exit gdb, enter ‘q’. This will return you to the terminal prompt.

If Module auto-recovery was disabled, re-enable it on the Manage Servers page.

Restart the programs using the appropriate method for the system you are working on.

Step 8: Provide the information to engineering

Self explanatory. Add the information to the bug ticket, or via email to the engineer that requested the information.

Related:

  • No Related Posts

NetScaler 12.1 : NSPEE Crashes and Reboots Continuously After Upgrading to 12.1.48.13

After upgrading firmware from 12.0-57.19 to 12.1-48.13, NetScaler NSPEE crashes and goes in to a continuous reboot loop. The crash is happening in nsbasemem_free when trying to check for “Dup free Condition”.

There’s no user impact, but this prevents firmware upgrade. Entering the single user mode, and reverting the kernel to 12.0-57.19 stops the reboot loop.

Back Trace

Sample 1

Program terminated with signal 11, Segmentation fault.

#0 0x000000000197802c in kill ()

(gdb) bt

#0 0x000000000197802c in kill ()

#1 0x000000000174af89 in ns_stub_kill (pid=1866, sig=11) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_libc_stubs.c:703

#2 0x0000000001749691 in nsppe_signal_handler (signo=<optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/nsppe_utils.c:375

#3 <signal handler called>

#4 nsbasemem_free (uaddr=0x1dbaca900, sz=128, ID=<optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_basemem.c:759

#5 0x000000000116df3c in ns_freemem (mp=0x1dbaca900 “”, memsz=0, ID=45) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_mem.c:616

#6 0x0000000000f31751 in ns_mp_run_ioctls_queued () at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_krpc.c:1487

#7 0x00000000015079ac in packet_engine () at /home/build/rs_121_48_11_RTM/usr.src/sys/nic/ns_pe.c:3627

#8 0x000000000174814d in ns_enter_main (argc=<optimized out>, argv=<optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/nsppe.c:890

#9 0x000000000174c329 in main (argc=-609441536, argv=0x0) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_libc_stub_main.c:28

(gdb) f 4

#4 nsbasemem_free (uaddr=0x1dbaca900, sz=128, ID=<optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_basemem.c:759

759 /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_basemem.c: No such file or directory.

(gdb) info args

uaddr = 0x1dbaca900

sz = 128

ID = <optimized out>

(gdb) info local

smdp = <optimized out>

mdp = 0x0

block_id = 1

inx = 0

mask = <optimized out>

addr = 7980493056

descp = 0x20b7e20 <ns_base_mem_descr_arr>

(gdb) set $ADDR=(unsigned long long)uadddr

No symbol “uadddr” in current context.

(gdb) set $ADDR=(unsigned long long)uaddr

(gdb) p $ADDR

$1 = 7980493056

(gdb) p/x $ADDR

$2 = 0x1dbaca900

(gdb) p/x *$ADDR

$3 = 0x0

(gdb) p $ADDR+sz

$4 = 7980493184

(gdb) p mdp

$5 = (ns_memdesc_t *) 0x0

(gdb) f 6

#6 0x0000000000f31751 in ns_mp_run_ioctls_queued () at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_krpc.c:1487

1487 /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_krpc.c: No such file or directory.

(gdb) info args

No arguments.

(gdb) info local

nsb_rec = 0x1dbaca900

(gdb) p ns_mp_ioctl_nsb_q.ns_cur_nsb

$6 = 0

(gdb) f 4

#4 nsbasemem_free (uaddr=0x1dbaca900, sz=128, ID=<optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_basemem.c:759

759 /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_basemem.c: No such file or directory.

(gdb) info args

uaddr = 0x1dbaca900

sz = 128

ID = <optimized out>

(gdb) info local

smdp = <optimized out>

mdp = 0x0

block_id = 1

inx = 0

mask = <optimized out>

addr = 7980493056

descp = 0x20b7e20 <ns_base_mem_descr_arr>

(gdb) p descp->memlist

$7 = (ns_memdesc_t *) 0x20b6a80 <nsmem_memlist>

(gdb) p descp->memlist.nmd_memlist

$8 = {{cle_next = 0x100000000}, {cle_prev = 0x1dbacae00}}

(gdb) p mdp->ns_memdesc_nmdaddr

Cannot access memory at address 0x0

Sample 2 :

(gdb) bt

#0 0x000000000197802c in kill () at /home/build/rs_121_48_11_RTM/usr.src/contrib/ustl/ustl-2.2/sistream.cc:123

#1 0x000000000174af89 in ns_stub_kill (pid=<value optimized out>, sig=<value optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_libc_stubs.c:703

#2 0x0000000001749691 in nsppe_signal_handler (signo=<value optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/nsppe_utils.c:375

#3 <signal handler called>

#4 nsbasemem_free (uaddr=0x11f3b9e80, sz=128, ID=<value optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_basemem.c:759

#5 0x000000000116df3c in ns_freemem (mp=0x11f3b9e80 “”, memsz=48, ID=45) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_mem.c:616

#6 0x0000000000f31751 in ns_mp_run_ioctls_queued () at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_krpc.c:1487

#7 0x00000000015079ac in packet_engine () at /home/build/rs_121_48_11_RTM/usr.src/sys/nic/ns_pe.c:3627

#8 0x000000000174814d in ns_enter_main (argc=<value optimized out>, argv=<value optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/nsppe.c:890

#9 0x000000000174c329 in main (argc=<value optimized out>, argv=<value optimized out>) at /home/build/rs_121_48_11_RTM/usr.src/sys/netscaler/ns_libc_stub_main.c:28

Current language: auto; currently c++

Messages Log :

Messages shows“unable to connect to nsnetsvc: Connection refused”

19:32:44 <local0.err> FH2-NETSCALER1 nsconfigd: _dispatch(): Connection failed

Jun 30 19:32:44 <local0.err> FH2-NETSCALER1 nsconfigd: _dispatch(): Connection failed

Jun 30 19:32:44 <local0.crit> FH2-NETSCALER1 nsconfigd: netsvcfd(): unable to connect to nsnetsvc: Connection refused

Jun 30 19:32:44 <local0.err> FH2-NETSCALER1 nsconfigd: _dispatch(): Connection failed

Jun 30 19:32:44 <local0.crit> FH2-NETSCALER1 nsconfigd: netsvcfd(): unable to connect to nsnetsvc: Connection refused

Jun 30 19:32:44 <local0.err> FH2-NETSCALER1 nsconfigd: _dispatch(): Connection failed

Jun 30 19:32:44 <local0.crit> FH2-NETSCALER1 nsconfigd: netsvcfd(): unable to connect to nsnetsvc: Connection refused

Jun 30 19:32:44 <local0.err> FH2-NETSCALER1 nsconfigd: _dispatch(): Connection failed

Jun 30 19:32:44 <local0.crit> FH2-NETSCALER1 nsconfigd: netsvcfd(): unable to connect to nsnetsvc: Connection refused

Jun 30 19:32:44 <local0.err> FH2-NETSCALER1 nsconfigd: _dispatch(): Connection failed

Jun 30 19:32:44 <local0.crit> FH2-NETSCALER1 nsconfigd: netsvcfd(): unable to connect to nsnetsvc: Connection refused

NS Log :

Ns.log is flooded with the message

cpu” – Status “Success”

Jul 1 10:00:58 <local0.info> FH2-NETSCALER1 httpd: Failed to open file:/flash/nsconfig/.callhome.conf, Permission denied

Jul 1 10:00:58 <local0.info> 10.17.172.207 07/01/2018:10:00:58 GMT FH2-NETSCALER1 0-PPE-0 : default API CMD_EXECUTED 4103 0 : User nsroot – Remote_ip 10.172.2.20 – Command “stat ssl” –

Status “Success”

Jul 1 10:01:59 <local0.info> FH2-NETSCALER1 httpd: Failed to open file:/flash/nsconfig/.callhome.conf, Permission denied

Jul 1 10:01:59 <local0.info> 10.17.172.207 07/01/2018:10:01:59 GMT FH2-NETSCALER1 0-PPE-0 : default API CMD_EXECUTED 4104 0 : User nsroot – Remote_ip 10.172.2.20 – Command “stat ns” –

Status “Success”

Jul 1 10:01:59 <local0.info> FH2-NETSCALER1 httpd: Failed to open file:/flash/nsconfig/.callhome.conf, Permission denied

Jul 1 10:01:59 <local0.info> 10.17.172.207 07/01/2018:10:01:59 GMT FH2-NETSCALER1 0-PPE-0 : default API CMD_EXECUTED 4105 0 : User nsroot – Remote_ip 10.172.2.20 – Command “stat system

” – Status “Success”

Jul 1 10:01:59 <local0.info> FH2-NETSCALER1 httpd: Failed to open file:/flash/nsconfig/.callhome.conf, Permission denied

Jul 1 10:01:59 <local0.info> 10.17.172.207 07/01/2018:10:01:59 GMT FH2-NETSCALER1 0-PPE-0 : default API CMD_EXECUTED 4106 0 : User nsroot – Remote_ip 10.172.2.20 – Command “stat system

memory” – Status “Success”

Jul 1 10:01:59 <local0.info> FH2-NETSCALER1 httpd: Failed to open file:/flash/nsconfig/.callhome.conf, Permission denied

Jul 1 10:01:59 <local0.info> 10.17.172.207 07/01/2018:10:01:59 GMT FH2-NETSCALER1 0-PPE-0 : default API CMD_EXECUTED 4107 0 : User nsroot – Remote_ip 10.172.2.20 – Command “stat system

cpu” – Status “Success

Related:

Re: Object content being dumped to logs

Let me start with apologizing for the lengthy post. Just want to make sure all the details are provided in one go…

We use com.emc.atmos.api.jersey.AtmosApiClient class to call getObjectMetadata and readObjectStream methods to retrieve the objects from the storage. Functionality is working absolutely fine and we don’t have any issue with that. However, on the catalina.out log file we see below log debug information for getObjectMetadata:

DEBUG: Connection request: [route: {}->http://<host>:<port>][total kept alive: 0; route allocated: 0 of 200; total allocated: 0 of 200]

DEBUG: Connection leased: [id: 1][route: {}->http://<host>:<port>][total kept alive: 0; route allocated: 1 of 200; total allocated: 1 of 200]

DEBUG: Connecting to <host>:<port>

DEBUG: CookieSpec selected: best-match

DEBUG: Target auth state: UNCHALLENGED

DEBUG: Proxy auth state: UNCHALLENGED

DEBUG: Attempt 1 to execute request

DEBUG: Sending request: HEAD /rest/objects/<object_ID> HTTP/1.1

DEBUG: >> “HEAD /rest/objects/<object_ID> HTTP/1.1[r][n]”

DEBUG: >> “x-emc-utf8: true[r][n]”

DEBUG: >> “Date: Mon, 9 Jul 2018 21:10:25 UTC[r][n]”

DEBUG: >> “x-emc-date: Mon, 9 Jul 2018 21:10:25 UTC[r][n]”

DEBUG: >> “x-emc-uid: <UID>[r][n]”

DEBUG: >> “x-emc-signature: <signature>[r][n]”

DEBUG: >> “Host: <host>:<port>[r][n]”

DEBUG: >> “Connection: Keep-Alive[r][n]”

DEBUG: >> “User-Agent: Apache-HttpClient/4.2.6 (java 1.5)[r][n]”

DEBUG: >> “[r][n]”

DEBUG: >> HEAD /rest/objects/<object_ID> HTTP/1.1

DEBUG: >> x-emc-utf8: true

DEBUG: >> Date: Mon, 9 Jul 2018 21:10:25 UTC

DEBUG: >> x-emc-date: Mon, 9 Jul 2018 21:10:25 UTC

DEBUG: >> x-emc-uid: <UID>

DEBUG: >> x-emc-signature: <signature>

DEBUG: >> Host: <host>:<port>

DEBUG: >> Connection: Keep-Alive

DEBUG: >> User-Agent: Apache-HttpClient/4.2.6 (java 1.5)

DEBUG: << “HTTP/1.1 200 OK[r][n]”

DEBUG: << “Date: Mon, 09 Jul 2018 21:10:19 GMT[r][n]”

DEBUG: << “x-emc-mtime: 1531164643814[r][n]”

DEBUG: << “x-emc-meta: <the_metadata>[r][n]”

DEBUG: << “x-emc-listable-meta: filename=Test%20New%20Download%20Cloud%20Storage.xlsx[r][n]”

DEBUG: << “x-emc-useracl: <uid>=FULL_CONTROL[r][n]”

DEBUG: << “x-emc-groupacl: other=READ[r][n]”

DEBUG: << “x-emc-policy: default[r][n]”

DEBUG: << “x-emc-utf8: true[r][n]”

DEBUG: << “x-emc-request-id: <request_id>[r][n]”

DEBUG: << “Content-Type: application/octet-stream[r][n]”

DEBUG: << “Content-Length: 1219856[r][n]”

DEBUG: << “[r][n]”

DEBUG: Receiving response: HTTP/1.1 200 OK

DEBUG: << HTTP/1.1 200 OK

DEBUG: << Date: Mon, 09 Jul 2018 21:10:19 GMT

DEBUG: << x-emc-mtime: 1531164643814

DEBUG: << x-emc-meta: <the_metadata>

DEBUG: << x-emc-listable-meta: filename=Test%20New%20Download%20Cloud%20Storage.xlsx

DEBUG: << x-emc-useracl: <uid>=FULL_CONTROL

DEBUG: << x-emc-groupacl: other=READ

DEBUG: << x-emc-policy: default

DEBUG: << x-emc-utf8: true

DEBUG: << x-emc-request-id: <request_id>

DEBUG: << Content-Type: application/octet-stream

DEBUG: << Content-Length: 1219856

DEBUG: Connection can be kept alive indefinitely

DEBUG: Connection [id: 1][route: {}->http://<host>:<port>] can be kept alive indefinitely

DEBUG: Connection released: [id: 1][route: {}->http://<host>:<port>][total kept alive: 1; route allocated: 1 of 200; total allocated: 1 of 200]

And for readObjectStream:

All of the above debug logs plus –

DEBUG: << Content-Type: application/octet-stream

DEBUG: << Content-Length: 1219856

DEBUG: Connection can be kept alive indefinitely

DEBUG: << “PK[0x3][0x4][0x14][0x0][0x8][0x8][0x8][0x0][0xd4]s[0xe9]L[0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x11][0x0][0x0][0x0]docProps/core.xml[0xad][0x91]MK[0xc4]0[0x10][0x86][0xef][0xfd][0x15]![0xf7]v[0xd2][0xad][0xe8][0x1a][0xda].[0xa2],[0x8][0x8a][0xb][0xae]([0xde]B:[0xb6][0xc5][0xe6][0x83]$[0xda][0xf5][0xdf][0x9b][0xed][0xae][0x15][0xc5][0xa3][0xc7][0xc9][0xfb][0xbc][0xf][0xc3][0xa4][0xed][0xd4]@[0xde][0xd1][0xf9][0xde][0xe8][0x8a][0xe6][0x19][0xa3][0x4][0xb5]4M[0xaf][0xdb][0x8a]>l[0xd7][0xe9][0x92][0xae][0xea]$)[0xa5]q[0xb8]q[0xc6][0xa2][0xb]=z[0x12][[0xda]W[0xb4][0xb][0xc1]r[0x0]/;T[0xc2]g1[0xd6]1y1N[0x89][0x10]G[0xd7][0x82][0x15][0xf2]U[0xb4][0x8][0xb][0xc6]NAa[0x10][0x8d][0x8][0x2][0xf6][0xb6][0xd4][0xce]:z[0xf0]qi[0xff]][0xd9][0xc8]Yi[0xdf][0xdc]0[0x9][0x1a][0x9]8[0xa0]B[0x1d]<[0xe4]Y[0xe][0xdf]l@[0xa7][0xfc][0x9f][0x85])[0x99][0xc9][0x9d][0xef]gj[0x1c][0xc7]l,&.n[0x94][0xc3][0xd3][0xed][0xcd][0xfd][0xb4]|[0xda]k[0x1f][0x84][0x96]H[0xeb][0x84][0x90][0xf2]h[0xe7][0xd2][0xa1][0x8][0xd8][0x90][0xe8][0xe0][0xe1][0xc3]bE[0xbf][0x92][0xc7][0xe2][0xf2]j[0xbb][0xa6][0xf5][0x82][0xe5][0xcb][0x94][0x9d][0xa5][0xec]|[0x9b][0x9f][0xf0][0x82]qV<[0x97][0xf0][0xab]t[0x1e]F[0xe3][0xea][0x8b]x[0x96][0xe][0xc9][0xe6][0xee]z[0x8f][0xce][0xcf]I[0x9]?[0xbf][0xae]N>[0x1]PK[0x7][0x8][0x9d][0xf0][0x7][0x1e][0x5][0x1][0x0][0x0][0xf4][0x1][0x0][0x0]PK[0x3][0x4][0x14][0x0][0x8][0x8][0x8][0x0][0xd4]s[0xe9]L[0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0xb][0x0][0x0][0x0]_rels/.rels[0xad][0x92][0xc1]N[0xc3]0[0xc][0x86][0xef]}[0x8a]([0xf7][0xd5][0xdd][0x90][0x10]BMwAH[0xbb]Mh<@H[0xdc]6j[0x13]G[0x89][0x7][0xe5][0xed][0x9][0x7][0x4]C[0xc]v[0xe0][0x18][0xe7][0xf7][0xe7]O[0xb2][0xdb][0xed][0xe2]g[0xf1][0x8c]);[n]”

DEBUG: << “J[0xae][0xeb]F[n]”

DEBUG: << “[0xc][0x86][0xac][0xb][0x83][0x92][0x8f][0x87][0xfb][0xd5][0x8d][0xdc]vU[0xd5]>[0xe0][0xac][0xb9]d[0xf2][0xe8]b[0x16][0xa5])d%G[0xe6]x[0xb][0x90][0xcd][0x88]^[0xe7][0x9a]”[0x86][0xf2][0xd3]S[0xf2][0x9a][0xcb]3[r][0x10][0xb5][0x99][0xf4][0x80][0xb0]i[0x9a]kH_[0x19][0xb2][0xab][0x84]8[0xc1][0x8a][0x9d]U2[0xed][0xec]Z[0x8a][0xc3]k[0xc4]K[0xf0][0xd4][0xf7][0xce][0xe0][0x1d][0x99][0xa3][0xc7][0xc0]?L[0xf9][0x96](d[0x9d][0x6]d%[0x97][0x19]^(MODS][0xa0][0x12][0xce][0xea]l[0xfe]S[0x7][0x17][0xc6]`[0xd1][0xae]b*[0xfd][0x89][0x1d][0xe6]O’Kf_[0xca][0x19]t[0x8c]H]].u~[0x5][0xe0][0x91][0xb5][0xd5][0xac][0xc1]P[0xc2][0xdf][0x95][0xde][0x13][0x1f]N-[0x9c]CW[0xbd][0x1]PK[0x7][0x8]W(^#[0xe3][0x0][0x0][0x0]F[0x2][0x0][0x0]PK[0x3][0x4][0x14][0x0][0x8][0x8][0x8][0x0][0xd4]s[0xe9]L[0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x13][0x0][0x0][0x0][Content_Types].xml[0xad][0x93][0xcb]N[0xc3]0[0x10]E[0xf7][0xf9][n]”

So basically the API is dumping even the binary content of the file to logs. This debug log is what we want to avoid being written to logs.

In order to fix this we created a log4j.properties file with entries shown below, made sure that the file is getting read properly by removing the entry log4j.appender.A1.layout from the file and we got a warning indicating this entry is missing. When I debug just before calling readObjectStream method the Atmos Client object created was (com.emc.atmos.api.jersey.AtmosApiClient) – So we tried to set the logger level to ERROR for this package – but still we can see all the binary content being dumped to catalina.out!! Any hints to solve this is greatly appreciated!! Thanks in advance.

# Set root logger level to DEBUG and its only appender to A1.

log4j.rootLogger=ERROR, A1

# A1 is set to be a ConsoleAppender.

log4j.appender.A1=org.apache.log4j.ConsoleAppender

# A1 uses PatternLayout.

log4j.appender.A1.layout=org.apache.log4j.PatternLayout

log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c %x – %m%n

# Print only messages of level INFO or above in the package com.emc.

log4j.logger.com.emc=ERROR

log4j.logger.com.emc.atmos.api.AtmosApi=ERROR

log4j.logger.com.emc.atmos.api.jersey=ERROR

Jars being used: atmos-client-3.0.1.jar, commons-httpclient-3.0.1.jar, jersey-apache-httpclient4-1.18-CUSTOM.jar

, jersey-client-1.19.jar, jersey-core-1.18.jar

Related:

Citrix RTOP 2.4: lync.exe freezes during a video call

Citrix support has a fix created after making changes so that GetProcessByID is called in debug build [LC9845]. Contact Citrix support to get the private fix.

Private File Disclaimer: This private fix (Private) was targeted only at your affected functionality, and regression and stress testing were minimal. Therefore, this fix might cause undesirable and unknown side effects. Introduce this Private to a test environment for evaluation before deploying it to a production environment. Your use of this Private is at your own risk. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CITRIX AND ITS SUPPLIERS MAKE AND YOU RECEIVE NO WARRANTIES OR CONDITIONS, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, AND CITRIX AND ITS SUPPLIERS SPECIFICALLY DISCLAIM WITH RESPECT TO THE PRIVATE ANY CONDITIONS OF QUALITY, AVAILABILITY, RELIABILITY, SECURITY, LACK OF VIRUSES, BUGS OR ERRORS, OR SUPPORT AND ANY IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT PERMITTED BY APPLICABLE LAW, NEITHER CITRIX, ITS SUPPLIERS SHALL BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL, MULTIPLE, PUNITIVE OR OTHER DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF DATA, LOSS OF INCOME, LOSS OF OPPORTUNITY, LOST PROFITS, COSTS OF RECOVERY OR ANY OTHER DAMAGES), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, AND WHETHER OR NOT FOR BREACH OF CONTRACT, NEGLIGENCE OR OTHERWISE, AND WHETHER OR NOT CITRIX, ITS SUPPLIERS, OR LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Citrix offers no assurance that this Private will be incorporated into the commercial version of the associated Citrix product or that it will work with future versions of such product.

Related:

ProxySG-restart issue

I need a solution

Hi Team,

We have noticed that proxy has restarted multiple times due to the bug. We have noticed below logs in the sysinfo.

Minicontext produced on: 2018-05-14 01:12:06+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.5.10.4.203460
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0x0
Software exception code: 0x10005
Page fault linear address: 0x0
Process group: “PG_UNKNOWN”
Process: “ATA Clock” in “” at .text+0x0

Minicontext produced on: 2018-05-13 12:24:32+00:00UTC
Minicontext version: 1.5
ProxySG Appliance: Version 6.5.10.4.203460
Architecture: x86_64
Kernel: Multiprocessor
System image flags: Customer, Optimized, Non-GDB, 64-bit

Hardware exception code: 0x0
Software exception code: 0x10005
Page fault linear address: 0x0
Process group: “PG_UNKNOWN”
Process: “ATA Clock” in “” at .text+0x0

We have noticed that the above bug:

Bug# 194940 – The ProxySG experienced a software restart at 0x10005 in process group “PG_UNKNOWN” in process “ATA Clock”.

But this issue has been fixed the version 6.5.5.1 but we are already running the version 6.5.10.4.

Please suggest us to fix this issue and provide the most stable veresion in this code.

Proxy Version: 6.5.10.4

Model: 600-20

Thanks,

Ram.

0

Related:

BE 2010 service terminates unexpectedly on windows server 2008 R2

I need a solution

Hi guys, we have BE 2010 run on our server for several years without any problems. Unfortunately, one problem appeared that BE server service terminated suddenly and the process beserver.exe quited. Any backup plan stopped too. We dig this problem for a few days and cannot get a resolution to address it.

We use ms windbg to analyze the dump

here is the output of windbg

Microsoft (R) Windows Debugger Version 6.7.0005.0
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:Program FilesSymantecBackup ExecBEDBGbeserver.exe_4280_0.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: SRV*C:Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Debug session time: Thu Mar 1 15:18:04.000 2018 (GMT+8)
System Uptime: not available
Process Uptime: 0 days 0:40:04.000
…………………………………………………………………………………………………………………………………………………………………………………
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(10b8.17a0): Access violation – code c0000005 (first/second chance not available)
ntdll!NtWaitForSingleObject+0xa:
00000000`774abd7a c3 ret
0:033> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** ERROR: Symbol file could not be found. Defaulted to export symbols for beserver.exe –
Unable to load image C:WindowsSystem32user32.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for user32.dll
*** ERROR: Module load completed but symbols could not be loaded for user32.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for beclass.dll –
*** ERROR: Symbol file could not be found. Defaulted to export symbols for beclass_mini.dll –
*** ERROR: Symbol file could not be found. Defaulted to export symbols for vxACE_3I.dll –
*** ERROR: Symbol file could not be found. Defaulted to export symbols for bemsdk.dll –
*** WARNING: Unable to verify checksum for mscorlib.ni.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for LIBVXVIMMAIL1I.DLL –

FAULTING_IP:
msvcr80!_output_s_l+855 [f:ddvctoolscrt_bldself_64_amd64crtsrcoutput.c @ 1648]
00000000`7503a955 803900 cmp byte ptr [rcx],0

EXCEPTION_RECORD: ffffffffffffffff — (.exr 0xffffffffffffffff)
ExceptionAddress: 000000007503a955 (msvcr80!_output_s_l+0x0000000000000855)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000007
Attempt to read from address 0000000000000007

PROCESS_NAME: beserver.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 – 0x%08lx

READ_ADDRESS: 0000000000000007

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

MANAGED_STACK: !dumpstack -EE
No export dumpstack found

LAST_CONTROL_TRANSFER: from 0000000075039725 to 000000007503a955

STACK_TEXT:
00000000`05417730 00000000`75039725 : 00000000`00000000 00000000`05418110 00000000`05419398 00000000`00000000 : msvcr80!_output_s_l+0x855 [f:ddvctoolscrt_bldself_64_amd64crtsrcoutput.c @ 1648]
00000000`05417a50 00000000`7503985e : 00000000`00000000 00000000`750d9f40 00000000`05417fa0 00000000`00eb0560 : msvcr80!vfprintf_helper+0x195 [f:ddvctoolscrt_bldself_64_amd64crtsrcvfprintf.c @ 69]
00000000`05417ab0 00000000`0091f6ae : 01d3b12d`7053e8a1 00000000`05417b60 00000000`00000000 00000000`00000000 : msvcr80!vfprintf_s+0x1e [f:ddvctoolscrt_bldself_64_amd64crtsrcvfprintf.c @ 127]
00000000`05417af0 00000000`009192f5 : 00000000`054180b0 00000000`004b7fa8 00000000`00000007 00000000`00000000 : beserver!DILoaderT >::operator=+0x30d1e
00000000`05417f90 00000000`0091cc29 : 00000000`054180b0 00000000`0000007f 00000000`0541a170 00000000`05418dc0 : beserver!DILoaderT >::operator=+0x2a965
00000000`05418050 00000000`750bbf40 : 00000000`0091cc10 00000000`0541b050 00000000`0541b050 00000000`7505964e : beserver!DILoaderT >::operator=+0x2e299
00000000`05418090 00000000`7505964e : 00000000`0091cc10 00000000`05419398 00000000`00000100 00000000`0000007f : msvcr80!_CallSettingFrame+0x20 [F:ddvctoolscrt_bldSELF_64_AMD64crtprebuildehAMD64handlers.asm @ 36]
00000000`054180b0 00000000`774ab681 : 00000000`00000000 00000000`0541a660 00000000`00000000 00000000`00000000 : msvcr80!__CxxCallCatchBlock+0xfe [f:ddvctoolscrt_bldself_64_amd64crtprebuildehframe.cpp @ 1342]
00000000`05418160 00000000`0091c800 : 00000000`00000000 00000000`004c9198 00000000`00eb0088 00000000`fffffff6 : ntdll!RcConsolidateFrames+0x3
00000000`0541b050 00000000`0091f0f5 : 00000000`00000001 00000000`00eb00c0 00000000`00000000 00000000`000001fc : beserver!DILoaderT >::operator=+0x2de70
00000000`0541fa90 00000000`0091f255 : 00000000`00eb00c0 00000000`00000000 00000000`00eb00c0 00000000`000001fc : beserver!DILoaderT >::operator=+0x30765
00000000`0541fed0 00000000`750237d7 : 00000000`000493e0 00000000`00000000 00000000`0317e620 00000000`00000000 : beserver!DILoaderT >::operator=+0x308c5
00000000`0541ff00 00000000`75023894 : 00000000`750d95c0 00000000`0317e620 00000000`00000000 00000000`00000000 : msvcr80!_callthreadstartex+0x17 [f:ddvctoolscrt_bldself_64_amd64crtsrcthreadex.c @ 348]
00000000`0541ff30 00000000`772559cd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msvcr80!_threadstartex+0x84 [f:ddvctoolscrt_bldself_64_amd64crtsrcthreadex.c @ 326]
00000000`0541ff60 00000000`7748a561 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`0541ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d

FOLLOWUP_IP:
msvcr80!_output_s_l+855 [f:ddvctoolscrt_bldself_64_amd64crtsrcoutput.c @ 1648]
00000000`7503a955 803900 cmp byte ptr [rcx],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: msvcr80!_output_s_l+855

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: msvcr80

IMAGE_NAME: msvcr80.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4dcdd833

FAULTING_THREAD: 00000000000017a0

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

PRIMARY_PROBLEM_CLASS: NULL_CLASS_PTR_DEREFERENCE

BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_DEREFERENCE

STACK_COMMAND: ~33s; .ecxr ; kb

FAILURE_BUCKET_ID: X64_APPLICATION_FAULT_NULL_CLASS_PTR_DEREFERENCE_msvcr80!_output_s_l+855

BUCKET_ID: X64_APPLICATION_FAULT_NULL_CLASS_PTR_DEREFERENCE_msvcr80!_output_s_l+855

Followup: MachineOwner
———

0:033> lmvm msvcr80
start end module name
00000000`75020000 00000000`750e9000 msvcr80 (private pdb symbols) C:Symbolsmsvcr80.AMD64.pdbF79035B45DFB4BB79DF9A0B8F5057FE51msvcr80.AMD64.pdb
Loaded symbol image file: msvcr80.dll
Mapped memory image file: C:Windowswinsxsamd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_88e41e092fab0294msvcr80.dll
Image path: C:Windowswinsxsamd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_88e41e092fab0294msvcr80.dll
Image name: msvcr80.dll
Timestamp: Sat May 14 09:17:39 2011 (4DCDD833)
CheckSum: 000CBCA1
ImageSize: 000C9000
File version: 8.0.50727.6195
Product version: 8.0.50727.6195
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Visual Studio® 2005
InternalName: MSVCR80.DLL
OriginalFilename: MSVCR80.DLL
ProductVersion: 8.00.50727.6195
FileVersion: 8.00.50727.6195
FileDescription: Microsoft® C Runtime Library
LegalCopyright: © Microsoft Corporation. All rights reserved.

0:033> k
Child-SP RetAddr Call Site
00000000`05416778 000007fe`fd5d10ac ntdll!NtWaitForSingleObject+0xa
00000000`05416780 00000000`0092c936 KERNELBASE!WaitForSingleObjectEx+0x79
00000000`05416820 00000000`0092ca7e beserver!DILoaderT >::operator=+0x3dfa6
00000000`05416880 000007fe`fa1b0b2d beserver!DILoaderT >::operator=+0x3e0ee
00000000`054168b0 00000000`772dbc10 mscorwks!InternalUnhandledExceptionFilter+0x1d
00000000`054168e0 00000000`774e0108 kernel32!UnhandledExceptionFilter+0x160
00000000`054169c0 00000000`77477958 ntdll! ?? ::FNODOBFM::`string’+0x2025
00000000`054169f0 00000000`7748812d ntdll!_C_specific_handler+0x8c
00000000`05416a60 00000000`7747855f ntdll!RtlpExecuteHandlerForException+0xd
00000000`05416a90 00000000`774abcb8 ntdll!RtlDispatchException+0x45a
00000000`05417170 00000000`7503a955 ntdll!KiUserExceptionDispatcher+0x2e
00000000`05417730 00000000`75039725 msvcr80!_output_s_l+0x855 [f:ddvctoolscrt_bldself_64_amd64crtsrcoutput.c @ 1648]
00000000`05417a50 00000000`7503985e msvcr80!vfprintf_helper+0x195 [f:ddvctoolscrt_bldself_64_amd64crtsrcvfprintf.c @ 69]
00000000`05417ab0 00000000`0091f6ae msvcr80!vfprintf_s+0x1e [f:ddvctoolscrt_bldself_64_amd64crtsrcvfprintf.c @ 127]
00000000`05417af0 00000000`009192f5 beserver!DILoaderT >::operator=+0x30d1e
00000000`05417f90 00000000`0091cc29 beserver!DILoaderT >::operator=+0x2a965
00000000`05418050 00000000`750bbf40 beserver!DILoaderT >::operator=+0x2e299
00000000`05418090 00000000`7505964e msvcr80!_CallSettingFrame+0x20 [F:ddvctoolscrt_bldSELF_64_AMD64crtprebuildehAMD64handlers.asm @ 36]
00000000`054180b0 00000000`774ab681 msvcr80!__CxxCallCatchBlock+0xfe [f:ddvctoolscrt_bldself_64_amd64crtprebuildehframe.cpp @ 1342]
00000000`05418160 00000000`0091c800 ntdll!RcConsolidateFrames+0x3

Any suggestions are appreciated.

0

Related: