Dead jace diagnose

**MaxBurn** · 07-01-2019, 08:50 AM

I have a dead NPM6E here returned from a site. Apparently this site has had multiple failures and this is the one where I was asking about the asd.jar file a while back. Trying to figure out what happened. Jace pings but there is no web page where there should be. Serial shell shows me this;

Code:

IPL for NPM 6-E (PPC440EP) v4.00-6.32 ECC

Press <ctrl-c> to stop autoboot...

Commands:
  0: serial
  1: on-board nand flash
  2: on-board nand flash (verbose)
  3: slot 1 nand option card
  4: slot 1 nand option card (verbose)
  5: sdram test, 1 iteration
  6: sdram test, continuous iterations
IPL>

Try again.

Commands:
  0: serial
  1: on-board nand flash
  2: on-board nand flash (verbose)
  3: slot 1 nand option card
  4: slot 1 nand option card (verbose)
  5: sdram test, 1 iteration
  6: sdram test, continuous iterations
IPL> 2
NAND00000001000000F1
ngi 00000028
ETFS_FS_2048
ifs image loaded 00000709 pages
Image load complete, starting image scan

Scanning flash at     0x02000000
Found image at        0x02000000
Jumping to startup at 0x002022D0
npm6xx startup version 7.00-6.41
Welcome to QNX Neutrino 6.4 on the NPM 6xx (ppc440)
fs-etfs-jace2048: readtrans BADBLK on cluster 27904
fs-etfs-jace2048: readtrans BADBLK on cluster 53632

Press ESC to choose alternate boot options...

continuing boot...

----------------------TCP/IP Network Status------------------------------
en0: flags=80008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,SHIM> mtu 1500
        address: 00:01:f0:8f:0a:08
        media: Ethernet none full-duplex
        status: active
        inet 192.168.1.123 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::201:f0ff:fe8f:a08%en0 prefixlen 64 tentative scopeid 0x2
-------------------------------------------------------------------------

NPM6-E with T2023 JACE-2 Base Board detected
SRAM mounted successfully at /sramopt
MESSAGE [06:58:49 01-Jul-2019] [tid = 2] niagarad: starting, baja_home=/niagara
MESSAGE [06:58:49 01-Jul-2019] [tid = 2] webserver: web server threads started [threadCount = 1]
MESSAGE [06:58:49 01-Jul-2019] [tid = 2] app registry: station registry starting
login:

Sounds like the memory is no good with those bad block messages?

This doesn't sound good;

Code:

Commands:
  0: serial
  1: on-board nand flash
  2: on-board nand flash (verbose)
  3: slot 1 nand option card
  4: slot 1 nand option card (verbose)
  5: sdram test, 1 iteration
  6: sdram test, continuous iterations
IPL> 5
memTestDevice from 0x00030000to 0x10000000

Try again.

Commands:
  0: serial
  1: on-board nand flash
  2: on-board nand flash (verbose)
  3: slot 1 nand option card
  4: slot 1 nand option card (verbose)
  5: sdram test, 1 iteration
  6: sdram test, continuous iterations
IPL> 5
memTestDevice from 0x00030000to 0x10000000

Try again.

Commands:
  0: serial
  1: on-board nand flash
  2: on-board nand flash (verbose)
  3: slot 1 nand option card
  4: slot 1 nand option card (verbose)
  5: sdram test, 1 iteration
  6: sdram test, continuous iterations
IPL>

Moving to a computer where I have workbench, seems that might have a chance of connecting to the platform anyway.

**MaxBurn** · 07-01-2019, 09:05 AM

This is everything I can see in application director, I wasn't able to catch the rest for some reason.

Code:

ead "Ping:AsdNetwork", waiting until one is available (attempt 1 of 3)
WARNING [13:19:02 08-May-19 EDT][platDataRecovery.service] No idle block available at time of flush on thread "Ping:AsdNetwork", waiting until one is available (attempt 1 of 3)
WARNING [13:19:03 08-May-19 EDT][platDataRecovery.service] No idle block available at time of flush on thread "server:worker", waiting until one is available (attempt 2 of 3)
WARNING [13:19:05 08-May-19 EDT][platDataRecovery.service] No idle block available at time of flush on thread "Ping:AsdNetwork", waiting until one is available (attempt 2 of 3)
WARNING [13:19:05 08-May-19 EDT][platDataRecovery.service] No idle block available at time of flush on thread "Ping:AsdNetwork", waiting until one is available (attempt 2 of 3)
WARNING [13:19:06 08-May-19 EDT][platDataRecovery.service] No idle block available at time of flush on thread "server:worker", waiting until one is available (attempt 3 of 3)
WARNING [13:19:08 08-May-19 EDT][platDataRecovery.service] No idle block available at time of flush on thread "Ping:AsdNetwork", waiting until one is available (attempt 3 of 3)
WARNING [13:19:08 08-May-19 EDT][platDataRecovery.service] No idle block available at time of flush on thread "Ping:AsdNetwork", waiting until one is available (attempt 3 of 3)
ERROR [13:19:09 08-May-19 EDT][platDataRecovery.service] Could not obtain an idle block when attempting to flush, a serious error has occured
java.lang.Exception: Stack trace
 at java.lang.Thread.dumpStack(Unknown Source)
 at com.tridium.platDataRecovery.BDataRecoveryService.doFlushRecoveryData(BDataRecoveryService.java)
 at com.tridium.platDataRecovery.BDataRecoveryService.append(BDataRecoveryService.java)
 at com.tridium.platDataRecovery.BDataRecoveryService.append(BDataRecoveryService.java)
 at com.tridium.history.BDataRecoveryHistoryRecorder.historyEvent(BDataRecoveryHistoryRecorder.java)
 at javax.baja.history.db.BHistoryDatabase.fireHistoryEvent(BHistoryDatabase.java)
 at com.tridium.history.db.BLocalDbHistory.append(BLocalDbHistory.java)
 at com.tridium.history.audit.BAuditHistoryService.audit(BAuditHistoryService.java)
 at com.tridium.sys.schema.ComplexSlotMap.audit(ComplexSlotMap.java)
 at com.tridium.sys.schema.ComplexSlotMap.audit(ComplexSlotMap.java)
 at com.tridium.sys.schema.ComplexSlotMap.set(ComplexSlotMap.java)
 at javax.baja.sys.BComplex.set(BComplex.java)
 at javax.baja.bacnet.export.BBacnetAnalogWritableDescriptor.writePriorityArray(BBacnetAnalogWritableDescriptor.java)
 at javax.baja.bacnet.export.BBacnetAnalogWritableDescriptor.writeProperty(BBacnetAnalogWritableDescriptor.java)
 at javax.baja.bacnet.export.BBacnetPointDescriptor.writeProperty(BBacnetPointDescriptor.java)
 at com.tridium.bacnet.stack.server.PropertyHandler.processWritePropertyMultipleRequest(PropertyHandler.java)
 at com.tridium.bacnet.stack.server.PropertyHandler.receiveRequest(PropertyHandler.java)
 at com.tridium.bacnet.stack.server.BBacnetServerLayer.processConfirmedRequest(BBacnetServerLayer.java)
 at com.tridium.bacnet.stack.server.BBacnetServerLayer.process(BBacnetServerLayer.java)
 at com.tridium.bacnet.stack.server.BBacnetServerLayer$ServerRequest.run(BBacnetServerLayer.java)
 at javax.baja.util.Worker.process(Worker.java)
 at javax.baja.util.Worker$Processor.run(Worker.java)
 at java.lang.Thread.run(Unknown Source)
ERROR [13:19:09 08-May-19 EDT][platDataRecovery.service] Flush operation failed.
ERROR [13:19:12 08-May-19 EDT][platDataRecovery.service] Could not obtain an idle block when attempting to flush, a serious error has occured
java.lang.Exception: Stack trace
 at java.lang.Thread.dumpStack(Unknown Source)
 at com.tridium.platDataRecovery.BDataRecoveryService.doFlushRecoveryData(BDataRecoveryService.java)
 at com.tridium.platDataRecovery.BDataRecoveryService.update(BDataRecoveryService.java)
 at com.tridium.dataRecovery.BDataRecoveryComponentRecorder.record(BDataRecoveryComponentRecorder.java)
 at com.tridium.sys.schema.ComplexSlotMap.set(ComplexSlotMap.java)
 at javax.baja.sys.BComplex.set(BComplex.java)
 at javax.baja.serial.BSerialHelper.setBaudRate(BSerialHelper.java)
 at com.ibms.asd.request.InitializeBaudRateReq.run(InitializeBaudRateReq.java)
 at com.ibms.asd.BAsdNetwork.setNetworkBaudRate(BAsdNetwork.java)
 at com.ibms.asd.BAsdMonitor.run(BAsdMonitor.java)
 at java.lang.Thread.run(Unknown Source)
ERROR [13:19:12 08-May-19 EDT][platDataRecovery.service] Flush operation failed.
ERROR [13:19:15 08-May-19 EDT][platDataRecovery.service] Could not obtain an idle block when attempting to flush, a serious error has occured
java.lang.Exception: Stack trace
 at java.lang.Thread.dumpStack(Unknown Source)
 at com.tridium.platDataRecovery.BDataRecoveryService.doFlushRecoveryData(BDataRecoveryService.java)
 at com.tridium.platDataRecovery.BDataRecoveryService.update(BDataRecoveryService.java)
 at com.tridium.dataRecovery.BDataRecoveryComponentRecorder.record(BDataRecoveryComponentRecorder.java)
 at com.tridium.sys.schema.ComplexSlotMap.modified(ComplexSlotMap.java)
 at com.tridium.sys.schema.ComplexSlotMap.set(ComplexSlotMap.java)
 at javax.baja.sys.BComplex.set(BComplex.java)
 at javax.baja.driver.ping.BPingHealth.setLastOkTime(BPingHealth.java)
 at javax.baja.driver.ping.BPingHealth.pingOk(BPingHealth.java)
 at javax.baja.driver.BDevice.pingOk(BDevice.java)
 at com.ibms.asd.BAsdDevice.doPing(BAsdDevice.java)
 at com.ibms.asd.BAsdMonitor.run(BAsdMonitor.java)
 at java.lang.Thread.run(Unknown Source)
ERROR [13:19:15 08-May-19 EDT][platDataRecovery.service] Flush operation failed.
ENGINE WATCHDOG TIMEOUT STACK DUMP @ Wed May 08 13:21:05 EDT 2019Full thread dump Java HotSpot(TM) Client VM (1.5.0_34-b28 mixed mode):

"/Services/JobService/StationSaveJob3" prio=5 tid=0x488ead10 nid=0x3b runnable [0x46399000..0x4639aac0]
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(Unknown Source)
 - locked <0x4abf8d78> (a java.net.SocksSocketImpl)
 at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
 at java.net.PlainSocketImpl.connect(Unknown Source)
 at java.net.SocksSocketImpl.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at sun.net.NetworkClient.doConnect(Unknown Source)
 at sun.net.www.http.HttpClient.openServer(Unknown Source)
 at sun.net.www.http.HttpClient.openServer(Unknown Source)
 - locked <0x4abf8eb8> (a sun.net.www.http.HttpClient)
 at sun.net.www.http.HttpClient.<init>(Unknown Source)
 at sun.net.www.http.HttpClient.New(Unknown Source)
 at sun.net.www.http.HttpClient.New(Unknown Source)
 at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
 at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
 - locked <0x4abf8f40> (a sun.net.www.protocol.http.HttpURLConnection)
 at java.net.HttpURLConnection.getResponseCode(Unknown Source)
 at com.tridium.platform.daemon.LocalSessionUtil.localDaemonIsAvailable(LocalSessionUtil.java)
 at com.tridium.platform.BSystemPlatformService$SaveListener.stationSaveOk(BSystemPlatformService.java)
 at com.tridium.sys.station.Station.saveOk(Station.java)
 at com.tridium.sys.station.Station.saveSync(Station.java)
 - locked <0x4975f5d8> (a java.lang.Object)
 at com.tridium.sys.station.Station.saveSync(Station.java)
 at com.tridium.sys.station.BStationSaveJob.run(BStationSaveJob.java)
 at javax.baja.job.BSimpleJob$JobThread.run(BSimpleJob.java)

"BSystemPlatformServiceQnx::failureRebootUpdateThread" prio=5 tid=0x48ba10f8 nid=0x3c runnable [0x46319000..0x4631a9c0]
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(Unknown Source)
 - locked <0x4abe5638> (a java.net.SocksSocketImpl)
 at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
 at java.net.PlainSocketImpl.connect(Unknown Source)
 at java.net.SocksSocketImpl.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at java.net.Socket.<init>(Unknown Source)
 at ja

**MaxBurn** · 07-01-2019, 09:28 AM

Ah crap, file system full maybe? What fills up in a jace?

/var/log didn't have anything in it.
/ffs0/niagara/stations really didn't have anything of a significant size in it under history or alarms.
/ffs0/niagara/stations/dataRecovery directory was full of things like 1202407.drdb 133kb files. 518 of them and that only works out to like just under 70MB?
/dev/mem shows file size 4,194,303KB. Seems big but normal for a copy of memory.

Code:

Platform summary for 192.168.1.123
----------------------------------

Daemon HTTP Port:     3011
Host ID:              Qnx-NPM6E-xxxx
Niagara Runtime:      nre-core-qnx-ppc (3.7.106.1)
Architecture:         ppc
Number of CPUs:       1
Model:                NPM6E
Module Contents:      runtime
Strip line nos.:      true
Operating System:     qnx-jace-npm6xx-etfs2048 (2.6.27)
Java Virtual Machine: sun-jre-qnx-ppc (Sun Microsystems Inc. 1.5.0.34.28)
Niagara Stations Enabled: enabled
Sedona Support:       unsupported
Niagara R2 Support:   unsupported
Platform SSL Support: disabled
Port:                 5011
Certificate:          tridium
Protocol:             SSLv3+TLSv1
System Home:          /niagara

Physical RAM  Free            Total         
                  218,240 KB      262,144 KB

Filesystem    Free            Total           Block Size    Files         Max Files   
  /ffs0                 2 KB      126,976 KB   2,048 bytes          1314          4096

Modules
  alarm (Tridium 3.7.106)
  app (Tridium 3.7.106)
  asd (IBMS 3.5.34)
  backup (Tridium 3.7.106)
  bacnet (Tridium 3.7.106)
  baja (Tridium 3.7.106.1)
  bajaScript (Tridium 3.7.106)
  bajaui (Tridium 3.7.106)
  basicDriver (Tridium 3.7.106)
  box (Tridium 3.7.106)
  bql (Tridium 3.7.106)
  chart (Tridium 3.7.106)
  control (Tridium 3.7.106)
  converters (Tridium 3.7.106)
  driver (Tridium 3.7.106)
  file (Tridium 3.7.106)
  fonts (Tridium 3.7.106)
  fox (Tridium 3.7.106.1)
  gx (Tridium 3.7.106)
  history (Tridium 3.7.106)
  html (Tridium 3.7.106)
  hx (Tridium 3.7.106)
  icons (Tridium 3.7.106)
  js (Tridium 3.7.106)
  kitPx (Tridium 3.7.106)
  lonworks (Tridium 3.7.106)
  net (Tridium 3.7.106)
  niagaraDriver (Tridium 3.7.106)
  niagaraVirtual (Tridium 3.7.106)
  nsh (Tridium 3.7.106)
  oro (Tridium 3.7.106)
  pdf (Tridium 3.7.106)
  platBacnet (Tridium 3.7.106)
  platDataRecovery (Tridium 3.7.106)
  platLon (Tridium 3.7.106)
  platMstp (Tridium 3.7.106)
  platPower (Tridium 3.7.106)
  platSerial (Tridium 3.7.106)
  platSerialQnx (Tridium 3.7.106)
  platform (Tridium 3.7.106)
  program (Tridium 3.7.106)
  query (Tridium 3.7.106)
  schedule (Tridium 3.7.106)
  serial (Tridium 3.7.106)
  tunnel (Tridium 3.7.44)
  wbutil (Tridium 3.7.106)
  web (Tridium 3.7.106.4)
  wiresheet (Tridium 3.7.106)
  workbench (Tridium 3.7.106)
  zwave (Tridium 3.7.106)

Other Parts
  npm6xx-etfs2048 (1.2)

Applications
  station xxxx autostart=false, autorestart=true, status=Idle

Lexicons

Licenses
  JENEsys.license (Tridium 3.7 - never expires)
  Lynxspring.license (Lynxspring 3.7 - never expires)

Certificates
  Lynxspring.certificate (Lynxspring - never expires)
  Tridium.certificate (Tridium - never expires)

**orion242** · 07-01-2019, 10:28 AM

Sounds like the data recovery bug.

Delete some / all of those files, reboot and then upgrade to the latest 3.7 version.

**MaxBurn** · 07-01-2019, 10:38 AM

Which file should I be deleting? I pulled back the entire station directory and it was only 68MB.

I see some other things that can go like lonworks.jar and zwave.jar.

**orion242** · 07-01-2019, 11:16 AM

Stuff in the data recovery folder. Normally dump it all, but if you want to be safe just get all the old files and keep the 3-4 most recent.

**MaxBurn** · 07-01-2019, 12:03 PM

Cleaned out the files and restarted, same issue. Application director said auto start was disabled. Told it to start and it started, looked normal until I saw tons of these errors scream by.

I don't think I saw the Asd Block Proxy Ext errors in the backup station I had.

I'm reasonably sure the Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow errors in that station backup I had and I resolved that by deleting exposed BACnet points for ASD equipment that didn't exist any more.

So it seems we might not have had to replace the actual jace here, hardware is OK? What about those memory tests that didn't come back and those BADBLK errors on serial shell?

Code:

ERROR [09:49:20 01-Jul-19 EDT][sys.engine] Cannot start component: Asd Block Proxy Ext
java.lang.NullPointerException
   at com.ibms.asd.point.BAsdBlockProxyExt.initProxyExt(BAsdBlockProxyExt.java)
   at com.ibms.asd.point.BAsdBlockProxyExt.started(BAsdBlockProxyExt.java)
   at com.tridium.sys.engine.EngineUtil.started(EngineUtil.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
ERROR [09:49:20 01-Jul-19 EDT][sys.engine] Cannot start component: Asd Block Proxy Ext
java.lang.NullPointerException
   at com.ibms.asd.point.BAsdBlockProxyExt.initProxyExt(BAsdBlockProxyExt.java)
   at com.ibms.asd.point.BAsdBlockProxyExt.started(BAsdBlockProxyExt.java)
   at com.tridium.sys.engine.EngineUtil.started(EngineUtil.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
ERROR [09:49:20 01-Jul-19 EDT][sys.engine] Cannot start component: Asd Block Proxy Ext
java.lang.NullPointerException
   at com.ibms.asd.point.BAsdBlockProxyExt.initProxyExt(BAsdBlockProxyExt.java)
   at com.ibms.asd.point.BAsdBlockProxyExt.started(BAsdBlockProxyExt.java)
   at com.tridium.sys.engine.EngineUtil.started(EngineUtil.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
ERROR [09:49:20 01-Jul-19 EDT][sys.engine] Cannot start component: Asd Block Proxy Ext
java.lang.NullPointerException
   at com.ibms.asd.point.BAsdBlockProxyExt.initProxyExt(BAsdBlockProxyExt.java)
   at com.ibms.asd.point.BAsdBlockProxyExt.started(BAsdBlockProxyExt.java)
   at com.tridium.sys.engine.EngineUtil.started(EngineUtil.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
ERROR [09:49:20 01-Jul-19 EDT][sys.engine] Cannot start component: Asd Block Proxy Ext
java.lang.NullPointerException
   at com.ibms.asd.point.BAsdBlockProxyExt.initProxyExt(BAsdBlockProxyExt.java)
   at com.ibms.asd.point.BAsdBlockProxyExt.started(BAsdBlockProxyExt.java)
   at com.tridium.sys.engine.EngineUtil.started(EngineUtil.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
   at com.tridium.sys.schema.ComponentSlotMap.start(ComponentSlotMap.java)
   at javax.baja.sys.BComponent.start(BComponent.java)
   at com.tridium.sys.engine.EngineManager.start(EngineManager.java)
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.heatDisable [binaryValue:156]: h:35d1
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.emsMorningWarmup [binaryValue:157]: h:35d3
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.emsOccupied [binaryValue:158]: h:35d5
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.emsCoolSetpoint [analogValue:390]: h:35d7
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.emsHeatSetpoint [analogValue:391]: h:35d9
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.emsUnoccHeatSetpoint [analogValue:392]: h:35db
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.occupancyStatus [binaryValue:159]: h:35e5
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.do1Status [binaryValue:160]: h:35e7
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.do3Status [binaryValue:161]: h:35eb
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.zoneTemp [analogValue:393]: h:35fd
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.boxFlow [analogValue:394]: h:35ff
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.coolOutput [analogValue:395]: h:3601
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.heatOutput [analogValue:396]: h:3603
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.auxTemp [analogValue:397]: h:3605
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.controlCoolSetpt [analogValue:398]: h:3607
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.controlHeatSetpt [analogValue:399]: h:3609
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.unoccHeatSetpt [analogValue:400]: h:360b
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.controlMaxFlow [analogValue:401]: h:360d
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.controlMinFlow [analogValue:402]: h:360f
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.flowSetpt [analogValue:403]: h:3615
WARNING [09:49:41 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_36_402.points.overrideTime [analogValue:404]: h:3619
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.heatDisable [binaryValue:288]: h:13918
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.emsMorningWarmup [binaryValue:289]: h:1391a
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.emsOccupied [binaryValue:290]: h:1391c
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.emsCoolSetpoint [analogValue:720]: h:1391e
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.emsHeatSetpoint [analogValue:721]: h:13920
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.emsUnoccHeatSetpoint [analogValue:722]: h:13922
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.occupancyStatus [binaryValue:291]: h:1392c
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.do1Status [binaryValue:292]: h:1392e
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.do3Status [binaryValue:293]: h:13932
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.zoneTemp [analogValue:723]: h:13944
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.boxFlow [analogValue:724]: h:13946
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.coolOutput [analogValue:725]: h:13948
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.heatOutput [analogValue:726]: h:1394a
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.auxTemp [analogValue:727]: h:1394c
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.controlCoolSetpt [analogValue:728]: h:1394e
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.controlHeatSetpt [analogValue:729]: h:13950
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.unoccHeatSetpt [analogValue:730]: h:13952
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.controlMaxFlow [analogValue:731]: h:13954
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.controlMinFlow [analogValue:732]: h:13956
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.flowSetpt [analogValue:733]: h:1395c
WARNING [09:49:43 01-Jul-19 EDT][bacnet.server] Unable to resolve point ord for Drivers.AsdNetwork.AsdMnFlow_58_414.points.overrideTime [analogValue:734]: h:13960
MESSAGE [09:49:48 01-Jul-19 EDT][web.server] HTTP Server started on port [80]
MESSAGE [09:49:49 01-Jul-19 EDT][fox] FOX server started on port [1911]
MESSAGE [09:49:49 01-Jul-19 EDT][sys] Niagara Runtime Environment: 3.7.106.1
MESSAGE [09:49:49 01-Jul-19 EDT][sys] *** Station Started (41638ms) [118418ms total] ***
niagara>MESSAGE [09:49:51 01-Jul-19 EDT][sys] Saving station...
WARNING [09:50:20 01-Jul-19 EDT][fox] Closing session [0: Server 192.168.1.200:55419 doesn't match opened session [null]
MESSAGE [09:50:27 01-Jul-19 EDT][fox] Opened: 1 <- 1 :: Workbench @ computer
MESSAGE [09:51:03 01-Jul-19 EDT][history.db] Saved history archive (280ms)
MESSAGE [09:51:05 01-Jul-19 EDT][sys] Saved /ffs0/niagara/stations/name/config.bog (73651ms)

**digo** · 07-01-2019, 12:58 PM

Originally Posted by MaxBurn

So it seems we might not have had to replace the actual jace here, hardware is OK? What about those memory tests that didn't come back and those BADBLK errors on serial shell?

fs-etfs-jace2048 BADBLK messages are normal, I'm told it's just the file system doing some routine maintenance.

As for the data recovery service, there's a thread on the niagara-community site with an explanation from one of Tridium's engineers.

https://www.niagara-community.com/_u...D5D000005DPJLK

**MaxBurn** · 07-01-2019, 01:27 PM

Good find there and I feel more assured the unit we sent out is going to be a long term fix as it was updated to the latest 3.7 mentioned there.

Funny thing, this jace had a battery in it all along.

**orion242** · 07-01-2019, 07:27 PM

Ditto on the bad blocks, seen this on more than one working unit.

If a Jace only boots to the IPL command line, its usually a door stop. If you can get to the full serial shell menu, its normally nothing that can't be dealt with.

On units with battery, I normally disable data recovery since it seemed to cause more harm than good. It seems they have gotten past the initial issues with it these days.

**MaxBurn** · 07-01-2019, 07:43 PM

Full serial shell menu like the ctrl-c one with the memory tests etc in it? Not sure which part you are referring to.

**orion242** · 07-01-2019, 07:52 PM

Full serial has the options to change the IP, reset platform creds, etc.

IPL is the IPL> command prompt. That's where the memory tests are. If the Jace only boots to that point, its warranty return or door stop. Platform is not running, cannot enable FTP, pretty screwed.

**MaxBurn** · 07-01-2019, 08:54 PM

Got it, thanks again.

Thread: Dead jace diagnose

Thread Tools

Search Thread

Display

Dead jace diagnose

vBulletin Message

Errors

The following errors occurred with your submission

Quick Reply

Register Now

Log-in

Posting Permissions