RE: Unparseable reply from gnatsd

Hello Chad,

Please ignore the below mail. Issue was in field value. “CC-List-Default” was required a default value and at the time of submit I was deleting that value and Hence the problem was.

Best Regards,

Vinod P

From: Vinod Kumar Pandey -X (vinodpan - TATA CONSULTANCY SERVICES LIMITED at Cisco)
Sent: Friday, February 15, 2019 10:49 AM
To: 'Chad Walstrom' <address@hidden>
Cc: address@hidden
Subject: RE: Unparseable reply from gnatsd

Hello Chad,

I appreciate on taking a look on my issue and thankful to you.

My gnats and gnats web version is as follows:

Gnatsweb v3.99.2, Gnats v4.2.0

Further, I have narrow down the issue. My customize dbconfig contains field “CC_List_Default”. PFA the dbconfig file which I am using at my end. If I comment out the CC-List-Default for the various mail format i.e.

1. mail-format "appended-email-response".

2. mail-format "initial-pr-notification-pending"

3. mail-format "audit-mail"

I didn’t get any issue of “Unparseable reply from gnatsd” it works as expected. I am not sure what is wrong in my configuration. Also is there any wiki page or Tutorial exist which I can refer to customize my dbconfig mail format.

But, I cann’t skip the “CC-list-Default” filed from the initial entry and its configuration as it important for us.

…

field "CC-List-Default" {

description "A COMMA separated list of email addresses to notify when this PR changes."

multitext { default "address@hidden" }

query-default inexact-regexp

textsearch

}

mail-format "initial-pr-notification" {

# Who the mail is from.

from-address {

"From:" | "From"

}

# We send mail to the responsible person, the addresses listed in

# the contact and notify fields of the submitter adm file entry for

# the Submitter-Id, and the notify person listed in the category

# adm file.

to-addresses {

"Responsible"

#"Submitter-Id[contact]"

#"Submitter-Id[notify]"

"Category[notify]"

"CC-List"

#"CC-List-Default"

}

# The reply-to address; either use the Reply-To: or From: header values

# from the PR, or the Submitter-Id's mail address.

reply-to {

#"Reply-To:" | "From:" | "Submitter-Id"

fixed-address "address@hidden"

}

# Any additional header text we want to add. Must have a newline at the

# end of each line.

header {

format "Subject: RER %s/%s: %s\nCc: %s\n"

fields { "Category" "Number" "Priority" "Subject:" }

}

body {

# Need to add this feature, or something like it.

# ($ExpireTime != "") {

# format "\tThe contract type is `%s' with a response time of %d business hours.\n"

# fields { "Submitter-Id[type]" "$ExpireTime" }

# }

# %P is "write the entire PR". Ugh. FIXME XXX ??? !!!

#format "%P"

format "%P\n\nhttp://bxb-mitg7-gnats:8080/cgi-bin/relengreq.pl?database=Releng-Requests&cmd=view+audit-trail&pr=%s\n"

# And if there's a %-format...there has to be an associated field.

# Double bleah.

#fields { "$" }

fields { "Number" }

}

…

mail-format "appended-email-response" {

from-address {

"$MailFrom"

}

# Should we send a copy to the user that sent in the message?

to-addresses {

"Responsible"

"Submitter-Id[contact]"

"CC-List"

#"CC-List-Default"

}

reply-to {

fixed-address "address@hidden"

#"$MailFrom"

}

header {

format "Subject: %s/%s: %s\n"

fields { "Category" "Number" "$MailSubject" }

}

body {

format "The following reply was made to PR %s/%s; it has been noted by GNATS.\n\n%s"

fields { "Category" "Number" "$NewAuditTrail" }

}

mail-format "audit-mail" {

from-address {

"$EditUserEmailAddr"

}

to-addresses {

"Responsible"

"$OldResponsible"

"Category[notify]"

"Submitter-Id[contact]"

"$EditUserEmailAddr"

"CC-List"

#"CC-List-Default"

"Reply-To:" | "From:" | "From"

}

# ??? Good question!

reply-to {

#fixed-address "bugs"

fixed-address "DO-NOT-REPLY-VIA-MAIL-USE-PR-ITSELF"

}

header {

format "Subject: RER %s/%s, %s, %s\n"

fields { "Category" "Number" "State" "Priority" }

}

body {

#format "Synopsis: %s\n\n%s\n"

format "Synopsis:%s\n\n%s\n\n\nhttp://bxb-mitg7-gnats:8080/cgi-bin/relengreq.pl?database=Releng-Requests&cmd=view+audit-trail&pr=%s\n"

fields { "Synopsis" "$NewAuditTrail" "Number" }

}

initial-entry {

fields {

"Originator" "CC-List" "CC-List-Default" "Synopsis" "UserId" "AccountType" "RepositoryAccessGroup" "Active-BranchName" "BuildNumber" "BuildSchedule"

"RepositoryName" "SuperRepoName" "RepoNoifyList" "Tag-Naming"

"ToBranch" "FromBranch" "QASchedule" "Remote-Sites" "Branch-Owner" "Needed-By"

"Priority" "Related-RER" "Category" "Description" "Branch-Description" "Branch-Restriction" "CDETS-Bugs" "Target-Branch-Retirement-Date"

"Add-Note-to-PR" "ASR-ParentBranch" "BranchPoint" "Customer" "Customer-Forums" "Announcement-Notes"

"ASR5000" "ASR5500" "ST20" "ST40" "VPC-SI" "VPC-DI" "EMS" "L-ESS" "IPMS" "P2P" "USP" "ULTRAM-MANAGER" "InPilot" "MURAL"

"Action" "WhatToDo" "Permissions" "Project" "AdditionalKey" "Has-Submodules" "RepositoryType" "SubModName" "CDETSPolicy"

"CDETS-Request-Type" "CDETS-Product" "CDETS-Component" "CDETS-Keyword" "CDETS-IsCustomerKeyword" "CDETS-DEManager" "CDETS-Version" "CDETS-Project" "CDETS-Class" "CDETS-Metadata-Item"

"Deployable" "CSDL-SI-Project"

}

Best Regards,

Vinod P

-----Original Message-----
From: Chad Walstrom [mailto:address@hidden]
Sent: Friday, February 15, 2019 7:27 AM
To: Vinod Kumar Pandey -X (vinodpan - TATA CONSULTANCY SERVICES LIMITED at Cisco) <address@hidden>
Cc: address@hidden
Subject: Re: Unparseable reply from gnatsd

Vinod Kumar Pandey -X (vinodpan - TATA CONSULTANCY SERVICES LIMITED atCisco) <address@hidden> writes:

> However, When I am trying to create a new PR while submitting on the

> web page I get an Error “Unparseable replay from gnatsd”.

Are you able to create tickets from the command-line tools? See if you can get a working environment set up with that first. I don't recall the Apache logs being all that helpful.

> I am new to gnats and don’t know how I can debug the issue. If any one

> has any ideas or a better way to trace down the problem please help

> me.

You can turn up the debugging level in gnatsweb, though I haven't look at that project in quite some time. You didn't mention which version of gnatsweb you were trying to use. The last one found in the Savannah download area was 4.00 from 2003. Richard Elberger posted in 2014 that he planned on rewriting Gnatsweb and had moved his development to

GitHub:

https://github.com/rpcme/GnatsWeb

He performed some clean-up on the package, but I do not see any significant changes to the software at this point.

Personally, I haven't looked at GNATS much beyond the last release, and there were a couple of point fixes made, I feel, in the repository that didn't make it to a release tarball. I made some local effort to migrate the commit history from CVS to git using sturgeon, but I didn't get to a point where I felt it was ready to share.

Chad Walstrom <address@hidden>

https://runswithd6s.gitlab.io/

From:	Vinod Kumar Pandey -X (vinodpan - TATA CONSULTANCY SERVICES LIMITED at Cisco)
Subject:	RE: Unparseable reply from gnatsd
Date:	Fri, 15 Feb 2019 07:24:19 +0000