[request error] [unhandled] [500] Status code: 500 when tried to chat with a created KB.

[wukong919]

Hit a new issue now:
Chat with knowledge base with id: 19
Knowledge base kb10 with embedding "nomic-embed-text:latest"
Creating embeddings for Ollama served model: nomic-embed-text:latest
Creating Chroma vector store
Initializing ParentDocumentRetriever with RedisDocstore
Redis client options: { host: 'redis', port: 6379, username: undefined, password: undefined }
Chat with Ollama, Host: http://host.docker.internal:11434
User query: connected vpc
Reformulated query: connected vpc
Relevant documents: [
Document {
pageContent: 'THE VPC CROSS-LINK AND CONNECTED VPC\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'Every production SDDC must be cross-linked to a VPC within the customer-owned AWS account, referred to as the connected VPC. This\n' +
'cross-linking is accomplished using the Cross-Account Elastic network interface\n' +
'[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html] (ENI) feature of AWS and creates a connection between every\n' +
'host within the management cluster of the SDDC to a subnet within the cross-linked VPC. This cross-link provides the SDDC with a\n' +
'high-bandwidth and low-latency network forwarding path to services maintained within the customer-owned AWS account.\n' +
'\n' +
'[data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==]',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'These VMkernel adapters are visible from the networking section of the configuration tab of the ESXi host. You can also get a sense\n' +
'of the setup by viewing the TCP/IP configuration for the host.\n' +
'\n' +
'The last portion of the underlay network are the virtual switches. Again, these are visible from the networking section of the\n' +
'configuration tab of the ESXi host. Here, you will see a mix of switches; some that are part of the underlay network and others\n' +
'which represent NSX network segments. The switches which are part of the underlay network are there to provide connectivity to the\n' +
'various management appliances of the SDDC. Of particular note is the management switch, which exists in order to provide the\n' +
'appliances with access to the management network. You can get a sense of some of the other important virtual switches in a host by\n' +
'examining their names as well as the management appliances which are attached to them.\n' +
'\n' +
'\n' +
'THE VPC CROSS-LINK AND CONNECTED VPC',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'The vCenter, NSX Managers and NSX edge appliances are typically deployed in the same AZ. In the event of an AZ failure, if\n' +
'vCenter, NSX Managers, and NSX edge appliances are in the impacted AZ, vSphere HA will restart these appliances and customers’\n' +
'workloads in the surviving AZ. These management appliances and NSX edge appliances will continue to operate there, even after the\n' +
'affected AZ is restored, until a failure or other scenario necessitates their recovery in another AZ. \n' +
'\n' +
'\n' +
'STRETCHED CLUSTER CONNECTED VPC\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'Stretched clusters require an Amazon VPC with two subnets, one subnet per availability zone. The subnets determine ESXi hosts\n' +
'placement between the two AZs. In the event that the active edge appliance migrates between hosts or AZs, the route tables of the\n' +
'connected VPC will be updated to route traffic through the appropriate cross-link ENI.\n' +
'\n' +
'[data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==]\n' +
'\n' +
'\n' +
'CROSS-AZ DATA FLOWS',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'The MTU size for Internet Uplink is 1500 bytes, which is not configurable.\n' +
'\n' +
'\n' +
'SERVICES UPLINK\n' +
'\n' +
'The services uplink connects the SDDC edge appliances to the connected VPC in the customer-owned AWS account. A static route on\n' +
'the SDDC edge appliances is configured for the primary CIDR of the VPC which points to the VPC router as a next hop during the\n' +
'SDDC provisioning. It enables compute workloads to leverage this uplink to consume AWS services and resources in the connected\n' +
'VPC. For services not running in the connected VPC, it is still possible to using the uplink to get connected through VPC\n' +
'endpoints [https://docs.aws.amazon.com/whitepapers/latest/aws-privatelink/what-are-vpc-endpoints.html].',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'VMware Cloud on AWS supports three types of compute network segments: routed, extended and disconnected.\n' +
'\n' +
'The difference of three network types is primarily in their connectivity capability:\n' +
'\n' +
' * Routed – routed (default type) network segments have connectivity to other segments within an SDDC and to external networks.\n' +
' * Extended – extended network segments are used with the NSX L2VPN to create a common broadcast domain between a VMware Cloud on\n' +
' AWS SDDC and on-premises networks.\n' +
' * Disconnected – disconnected network segments have no uplinks and create an isolated segment. Disconnected networks are\n' +
' primarily created by HCX, that can be changed to routed networks.\n' +
'\n' +
'For more information, please refer to Understanding Segments in VMC on AWS\n' +
'[https://vmc.techzone.vmware.com/understanding-segments-vmc-aws].\n' +
'\n' +
'\n' +
'CONNECTED VPC CONNECTIVITY',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'For more information, please refer to Understanding Segments in VMC on AWS\n' +
'[https://vmc.techzone.vmware.com/understanding-segments-vmc-aws].\n' +
'\n' +
'\n' +
'CONNECTED VPC CONNECTIVITY\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'Since we must always pass through the Edge SR whenever traffic leaves the SDDC, all traffic to and from the connected VPC must pass\n' +
'through the active edge appliance of the SDDC. Since this edge appliance is a VM, it resides on a specific ESXi host. As such, it\n' +
'will always use the Cross-Account ENI for that host. It should be noted that the hosts of the SDDC will be deployed within the\n' +
'same AZ as the cross-link subnet (the subnet which contains the Cross- Account ENIs). This mechanism controls the AZ placement of\n' +
'the SDDC (customer chooses the subnet and thus controls the AZ placement), but also serves to eliminate cross-AZ bandwidth charges\n' +
'between the edge and any native AWS resources within that same AZ.',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'ROUTE PRIORITY\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'When the NSX learns the same route from different sources, the NSX T0 router will choose the route based on its source in the\n' +
'following order:\n' +
'\n' +
' * Connected VPC\n' +
' * Route-based VPN (“Use VPN as backup to Direct Connect” is OFF)\n' +
' * Policy-based VPN *\n' +
' * VMware Transit Connect\n' +
' * Direct Connect Private VIF\n' +
' * Route-based VPN (“Use VPN as Backup to Direct Connect” is ON) \n' +
' * AWS Internet Gateway \n' +
'\n' +
'IPsec VPN will never be used for traffic from ESXi hosts if SDDC is a member of an SDDC Group or has a DX Private VIF attached.\n' +
'\n' +
' Use VPN as Backup to Direct Connect option is not applied to routes learned through VMware Transit Connect.\n' +
'\n' +
' Default Route only.\n' +
'\n' +
'\n' +
'NETWORK SERVICES\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'VPC PEERING FOR EXTERNAL STORAGE CONNECTION',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: ' Customers VPC connections are achieved through resource sharing from the VMware AWS account to the customer-owned AWS account.\n' +
' Once the VTGW resource sharing request is accepted in the customers AWS      Resource Access Manager, customer VPCs can be\n' +
' attached to VTGW through a VPC attachment from the AWS console. The attachment request must be accepted in VMware Cloud on AWS\n' +
' before the attachment is completed.\n' +
' * In terms of interconnectivity for customers AWS Transit Connect Gateways, these TGWs would be interconnected to VTGW through\n' +
' TGW peering. In a multi-region SDDC group, the choice of region for AWS TGW connection to is configurable.\n' +
" * Similarly, VTGW can be associated with customers DXGW through a TGW association. In the association configuration, 'allow\n" +
" prefixes' will be defined to specify which routes will be advertised to on-premises networks over the DXGW, with an AWS limit\n" +
' of up to 20 prefixes.',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'A screenshot of a computer

Description automatically generated\n' +
'[data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==]\n' +
'\n' +
'For more information about the AWS Managed Prefix List Mode, please refer to Understanding Managed Prefix List Mode for Connected\n' +
'VPC in VMC on AWS [https://vmc.techzone.vmware.com/understanding-managed-prefix-list-mode-connected-vpc-vmc-aws].\n' +
'\n' +
'\n' +
'EDGE UPLINKS\n' +
'\n' +
'There are currently three uplinks from the tier-0 routers of the SDDC. These are described below.\n' +
'\n' +
'\n' +
'INTERNET UPLINK\n' +
'\n' +
'The internet uplink is connected to AWS IGW within the underlay VPC. Since the default from other sources such as Direct Connect,\n' +
'IPSec VPN or VMware Transit Connect (VTC) has a higher priority, the IGW path would be only used when no other default routes are\n' +
'learned.',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: '[data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==]\n' +
'\n' +
'An internet gateway [https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Internet_Gateway.html] (IGW) and virtual private gateway\n' +
'[https://aws.amazon.com/directconnect/faqs/] (VGW) will also be created for this VPC. These gateways enable internet and Direct\n' +
"Connect connectivity to the VPC.  It's important to note that customers cannot directly see or manage these AWS components. Any\n" +
'interaction with or configuration of these components must be done through VMware-provided options such as the NSX UI, API, and\n' +
'Cloud Console.\n' +
'\n' +
'\n' +
'THE SDDC UNDERLAY\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'ESXI NETWORKING',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
}
]
Cohere Rerank Options: {
apiKey: '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',
baseUrl: 'http://peanutshell:8000/v1',
model: 'ms-marco-MiniLM-L-6-v2',
topN: 4
}
[nuxt] [request error] [unhandled] [500] Status code: 500
Body: "Internal Server Error"
at CohereClient. (./.output/server/node_modules/cohere-ai/Client.js:481:27)
at Generator.next ()
at fulfilled (./.output/server/node_modules/cohere-ai/Client.js:31:58)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5

Please help.

[sugarforever]

Looks it's some issue in the peanut-shell API.

Could you please try a couple of things at your end, following https://github.com/sugarforever/peanut-shell?

1. If the models endpoint works - curl --location 'http://localhost:8000/v1/models'
2. If the rerank endpoint works:

curl --location 'http://localhost:8000/v1/rerank/' \
--header 'Content-Type: application/json' \
--data '{
    "model": "ms-marco-MiniLM-L-6-v2",
    "query": "What is the capital of the United States?",
    "top_n": 3,
    "documents": [
        "Carson City is the capital city of the American state of Nevada.",
        "The Commonwealth of the Northern Mariana Islands is a group of islands in the Pacific Ocean. Its capital is Saipan.",
        "Washington, D.C. (also known as simply Washington or D.C., and officially as the District of Columbia) is the capital of the United States. It is a federal district.",
        "Capital punishment (the death penalty) has existed in the United States since beforethe United States was a country. As of 2017, capital punishment is legal in 30 of the 50 states."
    ]
}'

Please change the host localhost to your docker set up.

Let me know if you see any issue.

[sugarforever]

@wukong919 are you still experiencing the same issue? If not, I will close this issue.