HP Pavilion Entertainment PC suddenly does not start

Question

Some of my DAG are waiting to get scheduled, and some are waiting in the queue. I suspect there are reasons for this delay but not sure how I can start to debug this problem. Majority of the pipelines are running Spark jobs.

Can someone help to give me some directions in terms of where to look at to 1) anaylse which DAGs were delayed (did not start at the scheduled time) 2) where are the places I should look at to find out if the resources are enough. I'm quite new to scheduling in Airflow. Many thanks. Please let me know if I can describe the question better.

Solution

Here are the error codes for the blinking Caps Lock/Num Lock LEDs

This is a live link for Blank Screen LED Error Code

Component Tested Error Condition

LEDs blink 1 time CPU CPU not functional

LEDs blink 2 times BIOS BIOS corruption failure

LEDs blink 3 times Memory Module error not functional

LEDs blink 4 times Graphics Graphics controller not functional

LEDs blink 5 times System board General system board failure

LEDs blink 6 times BIOS BIOS authentication failure

I have seen two of these lately and both were system board failures.

Comments

[Matthew Williams]

This is likely some form of hardware problem. Have you done anything with your computer recently like change Memory. I would also suggest trying it on the mains power without the battery plugged in.

[Vanadis]

h10010.www1.hp.com/ewfrf/wc/… Here's a list of HP Pavilion error codes.

[Peter Fowler]

Try disconnecting mains power, take battery out, turn on to discharge any remaining power. Replace battery and try to reboot. Good luck !

[Skippy Fastol]

@MatthewWilliams: the computer is only on main power without battery...

[Skippy Fastol]

@Vanadis : your answer will solve my problem. Please post it as answer so I can validate it. 1000000 thanks.

[Skippy Fastol]

And how about if the blinking keeps without stopping ... ? :(

[Dave M]

In the cases I have seen the lights blink X times and then there is a noticeable pause and then the lights blink X times again. This continues until you power down. You will need to watch carefully. Given the number of threads on HP and other sites, there seems to be an issue with this model.

[fixer1234]

This isn't really a reliable solution. You just lucked out that, in your case, it's adequate to stop the symptoms. BTW, try baking only as a last resort when you plan to trash the motherboard, anyway, so you have nothing to lose.

[user4046073]

thanks yes I've had a look at the metadata, however I still struggling of getting the right columns to use, for example to find out the delayed dag, I tried to calculate (queued_dttm- execution_date) to see how long after the scheduled execution time it was queued. But whenever the dag was trigger manually, the queued_dttm would be overwritten..

[Thom Bedford]

@user4046073 Check the dag_run table instead of the dag table, there's a new record for every time the DAG is executed. Filter by the run_type column, that'll tell you if it's SCHEDULED or MANUAL, then you can compare the queued_at and start_date columns I believe. Again, depends on your Airflow version though. If the above doesn't apply, try the task_instance table.

[user4046073]

Thank you! Does is_paused mean the ones that are not running? They paused because they are not scheduled? or could it be possible for some other reason?

[user4046073]

thanks. when a run was cleared, run_type would also show as SCHEDULED, right?

[dimButTries]

@user4046073 is_paused based on my experience are those that have been deactivated/paused in the web UI via the toggle or CLI.

[Thom Bedford]

@user4046073 If that instance that you cleared was a scheduled run, then it will. If you executed the DAG manually and then cleared it, it'll show as MANUAL.