Hello all!
In my laptop env I have TD 13.10 version. After some reboots, Teradata didn’t start properly. So, when I issued
s10-1310:~ # pdestate -a PDE state: DOWN/HARDSTOP s10-1310:~ # /etc/init.d/tpa start Teradata Database Initiator service is starting... Teradata Database Initiator service started successfully. s10-1310:~ # pdestate -a PDE state: DOWN/HARDSTOP
Interesting…
So, I began reading OS logs first. Check out this:
/var/log/messages:
Aug 19 15:21:49 s10-1310 recond[5749]: INFO: TdatTools: 29001 #Current Working Directory set: /var/opt/teradata/tddump Aug 19 15:21:49 s10-1310 recond[5749]: INFO: TdatTools: 29001 #TPA START: "recond -S", NODE UPTIME: 0 Days, 0 Hours, 4 Minutes, 3 Seconds Aug 19 15:21:49 s10-1310 recond[5749]: INFO: TdatTools: 29001 #BOOT DETECT: seconds(243) is less than g->t1_boot_time_interval: 300 Aug 19 15:21:49 s10-1310 recond[5749]: INFO: TdatTools: 29001 #PDESLEEP( g->t3_boot_time_small_delay: 60 ) Aug 19 15:22:49 s10-1310 recond[5749]: DEGRADED: TdatTools: 29003 #PdeMain NOT started, PANIC-LOOP-DETECTED. Please delete file "/var/opt/teradata/tdtemp/PanicLoopDetected", after resolving the panic issue.
I deleted this file and now, everything works fine! So, be careful with reboots. Now, you are know how resolve this issue.
Regards,
Pavel.
Many thanks. I had the same problem with TD 14. deleting “/var/opt/teradata/tdtemp/PanicLoopDetected” solved the problem.
By: Nick Hoare on December 5, 2012
at 6:37 pm
Thanks.. It worked 🙂
By: Sat on December 13, 2012
at 7:04 pm
Здравствулте!
You should check what caused the panic state before starting PDE.Panic state is not peanuts! 😉
Пока
карлос
By: CarlosAL on March 12, 2013
at 2:33 pm
You are welcome! 🙂
By: Pavel Ermakov on April 11, 2013
at 3:44 pm
Great job, Pavel! I’ve had the same issue with TD14 VM!
Thank you
By: Sergey P on April 11, 2013
at 3:47 pm
Thanks Pavel !! It really saved my day…
By: prax on April 18, 2013
at 12:33 pm
Pasha, Thank you!
By: nonsleepr on July 31, 2013
at 2:16 pm