[WebDNA] Interesting Trigger issue

This WebDNA talk-list message is from

2020


It keeps the original formatting.
numero = 115122
interpreted = N
texte = 2751 This is a multi-part message in MIME format. --------------4CD6F6D0F86F753223570540 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hello all, I just wanted to document something I realized about Triggers. The WebDNA archives mention many times when Triggers inexplicably=20 stopped working, and I've been one of those reporting the problem a few=20 times since 1997. Two days ago the triggers stopped working for one of my sandboxes with=20 all the usual symptoms.=C2=A0 I tryed the typical troubleshooting of dele= ting=20 and readded the trigger record.=C2=A0 Then I deleted the Triggers.db and=20 replaced it.=C2=A0 I even tried to use a different sandbox.=C2=A0 I added= =20 [sendmail] as the first line of the .update.tpl file that was supposed=20 to be executed (even thought there were already 3 existing [sendmail]=20 further down).=C2=A0 All the while I was watching the trigger time updati= ng=20 correctly but the trigger wasn't running. I gave up and started writing a curl script for a cron job when I=20 discovered that the curl would not work either.=C2=A0 Running curl in ver= bose=20 mode I discovered that my server was resolving the wrong IP address for=20 the website. Digging further I found that my client's domain DNS records listed 4 DNS=20 servers.=C2=A0 1 of the servers was offline and 1 of them had the wrong I= P on=20 the A record. As it turned out, the server itself had cached the wrong IP for the=20 domain when I rebooted it 3 days ago.=C2=A0 The triggers came back to lif= e=20 once I updated the DNS record with the correct IP and removed the dead=20 DNS from the NS record list. Oddly enough, my own person adage of /"If nothing seems to make sense,=20 check the DNS"/ held true.=C2=A0 This was the first time I had problem wi= th=20 triggers since upgrading to WebDNA 8.x.=C2=A0 I'm really happy it wasn't = a=20 WebDNA issue after all. Hopefully this helps someone else who is pulling their hair out with=20 this issue in the future. -Matt --=20 Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator matt@psiprime.com Psi Prime 323 Union Blvd. Totowa, NJ 07512 Direct: 888.872.0274 Fax: 888.488.5924 http://www.perosi.com --------------4CD6F6D0F86F753223570540 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello all,

I just wanted to document something I realized about Triggers.

The WebDNA archives mention many times when Triggers inexplicably stopped working, and I've been one of those reporting the problem a few times since 1997.

Two days ago the triggers stopped working for one of my sandboxes with all the usual symptoms.=C2=A0 I tryed the typical troubleshootin= g of deleting and readded the trigger record.=C2=A0 Then I deleted the Triggers.db and replaced it.=C2=A0 I even tried to use a different sandbox.=C2=A0 I added [sendmail] as the first line of the .update.tp= l file that was supposed to be executed (even thought there were already 3 existing [sendmail] further down).=C2=A0 All the while I wa= s watching the trigger time updating correctly but the trigger wasn't running.

I gave up and started writing a curl script for a cron job when I discovered that the curl would not work either.=C2=A0 Running curl in verbose mode I discovered that my server was resolving the wrong IP address for the website.=C2=A0

Digging further I found that my client's domain DNS records listed 4 DNS servers.=C2=A0 1 of the servers was offline and 1 of them had the wrong IP on the A record.

As it turned out, the server itself had cached the wrong IP for the domain when I rebooted it 3 days ago.=C2=A0 The triggers came back to life once I updated the DNS record with the correct IP and removed the dead DNS from the NS record list.

Oddly enough, my own person adage of "If nothing seems to make sense, check the DNS" held true.=C2=A0 This was the first time = I had problem with triggers since upgrading to WebDNA 8.x.=C2=A0 I'm re= ally happy it wasn't a WebDNA issue after all.

Hopefully this helps someone else who is pulling their hair out with this issue in the future.

-Matt
--=20Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & Educatorm=att@psiprime.comPsi Prime323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://=www.perosi.com
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --------------4CD6F6D0F86F753223570540-- . Associated Messages, from the most recent to the oldest:

    
  1. RE: [WebDNA] Interesting Trigger issue ("Scott @ Itsula" 2020)
  2. [WebDNA] Interesting Trigger issue ("Matthew A Perosi, Psi Prime" 2020)
2751 This is a multi-part message in MIME format. --------------4CD6F6D0F86F753223570540 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hello all, I just wanted to document something I realized about triggers. The WebDNA archives mention many times when triggers inexplicably=20 stopped working, and I've been one of those reporting the problem a few=20 times since 1997. Two days ago the triggers stopped working for one of my sandboxes with=20 all the usual symptoms.=C2=A0 I tryed the typical troubleshooting of dele= ting=20 and readded the trigger record.=C2=A0 Then I deleted the triggers.db and=20 replaced it.=C2=A0 I even tried to use a different sandbox.=C2=A0 I added= =20 [sendmail] as the first line of the .update.tpl file that was supposed=20 to be executed (even thought there were already 3 existing [sendmail]=20 further down).=C2=A0 All the while I was watching the trigger time updati= ng=20 correctly but the trigger wasn't running. I gave up and started writing a curl script for a cron job when I=20 discovered that the curl would not work either.=C2=A0 Running curl in ver= bose=20 mode I discovered that my server was resolving the wrong IP address for=20 the website. Digging further I found that my client's domain DNS records listed 4 DNS=20 servers.=C2=A0 1 of the servers was offline and 1 of them had the wrong I= P on=20 the A record. As it turned out, the server itself had cached the wrong IP for the=20 domain when I rebooted it 3 days ago.=C2=A0 The triggers came back to lif= e=20 once I updated the DNS record with the correct IP and removed the dead=20 DNS from the NS record list. Oddly enough, my own person adage of /"If nothing seems to make sense,=20 check the DNS"/ held true.=C2=A0 This was the first time I had problem wi= th=20 triggers since upgrading to WebDNA 8.x.=C2=A0 I'm really happy it wasn't = a=20 WebDNA issue after all. Hopefully this helps someone else who is pulling their hair out with=20 this issue in the future. -Matt --=20 Matthew A Perosi Corporate Consultant Mobile Marketing Expert Senior Web Developer SEO Analyst & Educator matt@psiprime.com Psi Prime 323 Union Blvd. Totowa, NJ 07512 Direct: 888.872.0274 Fax: 888.488.5924 http://www.perosi.com --------------4CD6F6D0F86F753223570540 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello all,

I just wanted to document something I realized about triggers.

The WebDNA archives mention many times when triggers inexplicably stopped working, and I've been one of those reporting the problem a few times since 1997.

Two days ago the triggers stopped working for one of my sandboxes with all the usual symptoms.=C2=A0 I tryed the typical troubleshootin= g of deleting and readded the trigger record.=C2=A0 Then I deleted the triggers.db and replaced it.=C2=A0 I even tried to use a different sandbox.=C2=A0 I added [sendmail] as the first line of the .update.tp= l file that was supposed to be executed (even thought there were already 3 existing [sendmail] further down).=C2=A0 All the while I wa= s watching the trigger time updating correctly but the trigger wasn't running.

I gave up and started writing a curl script for a cron job when I discovered that the curl would not work either.=C2=A0 Running curl in verbose mode I discovered that my server was resolving the wrong IP address for the website.=C2=A0

Digging further I found that my client's domain DNS records listed 4 DNS servers.=C2=A0 1 of the servers was offline and 1 of them had the wrong IP on the A record.

As it turned out, the server itself had cached the wrong IP for the domain when I rebooted it 3 days ago.=C2=A0 The triggers came back to life once I updated the DNS record with the correct IP and removed the dead DNS from the NS record list.

Oddly enough, my own person adage of "If nothing seems to make sense, check the DNS" held true.=C2=A0 This was the first time = I had problem with triggers since upgrading to WebDNA 8.x.=C2=A0 I'm re= ally happy it wasn't a WebDNA issue after all.

Hopefully this helps someone else who is pulling their hair out with this issue in the future.

-Matt
--=20Matthew A PerosiCorporate ConsultantMobile Marketing ExpertSenior Web DeveloperSEO Analyst & Educatorm=att@psiprime.comPsi Prime323 Union Blvd.Totowa, NJ 07512Direct:  888.872.0274Fax:     888.488.5924http://=www.perosi.com
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --------------4CD6F6D0F86F753223570540-- . "Matthew A Perosi, Psi Prime"

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Hyperboard/bulletin board available (1998) WebCat2b15MacPlugin - showing [math] (1997) WebCat2b15MacPlugin - [protect] (1997) All orders are failing (2002) Can't Update records (1997) Email notification to one of multiple vendors ? (1997) Faxing orders in place of email (1997) problem serving foreign languages text (1997) Hyperboard/bulletin board available (1998) show all problem (1997) Resolving variables into field names (1998) Customer - again (1998) Re1000001: Setting up shop (1997) Banner DNA (1997) using listfiles to build a database? more (2000) Re:Change WebDNA-Talk Mail due to no digest for 1wk (1997) Using Grep to Format Text (2001) Searching multiple fields (1997) Re:Searching for ALL / empty form field (1997) Practical Uses (2003)